Páginas (390)

<property name="body">&lt;ac:structured-macro ac:macro-id="ee8f5ec1-26b7-4536-8c96-8b2ae74ca296" ac:name="section" ac:schema-version="1"&gt;&lt;ac:rich-text-body&gt;

&lt;ac:structured-macro ac:macro-id="4d25f1cb-65b3-4908-b435-2d6684f84e86" ac:name="column" ac:schema-version="1"&gt;&lt;ac:parameter ac:name="width"&gt;50%&lt;/ac:parameter&gt;&lt;ac:rich-text-body&gt;

&lt;ac:structured-macro ac:macro-id="cef12caa-0f75-428f-a923-69a9143decdc" ac:name="info" ac:schema-version="1"&gt;&lt;ac:parameter ac:name="title"&gt;Description&lt;/ac:parameter&gt;&lt;ac:rich-text-body&gt;
&lt;p&gt;Misc. Linux documentation. When we find something useful regarding Linux that we might use again, it should get documented here.&lt;/p&gt;&lt;/ac:rich-text-body&gt;&lt;/ac:structured-macro&gt;

&lt;p&gt;&lt;ac:structured-macro ac:macro-id="ea7473a7-f7df-4503-afa8-82458a003a9d" ac:name="livesearch" ac:schema-version="1"&gt;&lt;ac:parameter ac:name="spaceKey"&gt;&lt;ri:space ri:space-key="linux" /&gt;&lt;/ac:parameter&gt;&lt;ac:parameter ac:name="id"&gt;1&lt;/ac:parameter&gt;&lt;/ac:structured-macro&gt;&lt;/p&gt;
&lt;/ac:rich-text-body&gt;&lt;/ac:structured-macro&gt;
&lt;ac:structured-macro ac:macro-id="52f18322-60be-4521-81e5-6f52811ba01d" ac:name="column" ac:schema-version="1"&gt;&lt;ac:parameter ac:name="width"&gt;50%&lt;/ac:parameter&gt;&lt;ac:rich-text-body&gt;

&lt;ac:structured-macro ac:macro-id="d74e1da8-bbf6-4b62-a824-a84bd5076a4b" ac:name="recently-updated" ac:schema-version="1" /&gt; 
&lt;/ac:rich-text-body&gt;&lt;/ac:structured-macro&gt;
&lt;/ac:rich-text-body&gt;&lt;/ac:structured-macro&gt;</property>
    

<property name="body">&lt;p&gt;Sometimes, you have an ISO you've downloaded which you would like to access in linux, but don't want to go to the hassle of burning it.  The following command will allow you to mount it and read from it just like a CD:&lt;/p&gt;

&lt;p&gt;mount -o loop &lt;em&gt;filename&lt;/em&gt;.iso /mnt/&lt;em&gt;yourdirectory&lt;/em&gt;&lt;/p&gt;
</property>
    

<property name="body">&lt;h2&gt;First Step&lt;/h2&gt;&lt;h5&gt;If IP is assigned by DHCP, make sure /etc/hosts file looks like this:&lt;/h5&gt;&lt;ac:structured-macro ac:macro-id="0ed5ac2d-595b-46ad-85c4-bcaf839a435b" ac:name="code" ac:schema-version="1"&gt;&lt;ac:parameter ac:name="title"&gt;/etc/hosts&lt;/ac:parameter&gt;&lt;ac:parameter ac:name="borderStyle"&gt;solid&lt;/ac:parameter&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[Red Hat:
127.0.0.1     servername.suu.edu     localhost.localdomain     localhost     servername]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;h5&gt;If IP is hard-coded, make sure /etc/hosts file looks like this (x.x is your new IP):&lt;/h5&gt;&lt;ac:structured-macro ac:macro-id="8b6fdc65-ea3d-49ad-ba14-5229ca47a324" ac:name="code" ac:schema-version="1"&gt;&lt;ac:parameter ac:name="title"&gt;/etc/hosts&lt;/ac:parameter&gt;&lt;ac:parameter ac:name="borderStyle"&gt;solid&lt;/ac:parameter&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[Red Hat:
127.0.0.1     localhost.localdomain     localhost
134.250.x.x   yourserver.suu.edu        yourserver

 
Ubuntu:
127.0.0.1       localhost
127.0.1.1       yourserver
# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;h2&gt;UBUNTU Step - populate /etc/hostname with short hostname&lt;/h2&gt;&lt;ac:structured-macro ac:macro-id="d0b618dc-7740-485c-bfcd-674c630897be" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[yourserver]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;h2&gt;Second Step&lt;/h2&gt;&lt;h5&gt;If you need the change to happen immediately without a reboot, run the following command as root:&lt;/h5&gt;&lt;ac:structured-macro ac:macro-id="b9b0a424-edd9-4ace-a06c-3260d5bffe5f" ac:name="code" ac:schema-version="1"&gt;&lt;ac:parameter ac:name="borderStyle"&gt;solid&lt;/ac:parameter&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[#hostname yourserver.suu.edu
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;h2&gt;Third Step&lt;/h2&gt;&lt;h5&gt;This step is optional, and depends on the linux distribution and version you are using. If you have an /etc/HOSTNAME file, ensure that it is populated with a single line as follows:&lt;/h5&gt;&lt;ac:structured-macro ac:macro-id="82e6c63c-c07b-4172-b2be-d7715b9438c7" ac:name="code" ac:schema-version="1"&gt;&lt;ac:parameter ac:name="borderStyle"&gt;solid&lt;/ac:parameter&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[yourserver.suu.edu
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;h2&gt;Fourth Step&lt;/h2&gt;&lt;h5&gt;Edit the /etc/sysconfig/network file HOSTNAME line to read:&lt;/h5&gt;&lt;ac:structured-macro ac:macro-id="b8f89b25-1558-4906-9c4f-1b416b722c7a" ac:name="code" ac:schema-version="1"&gt;&lt;ac:parameter ac:name="title"&gt;/etc/sysconfig/network&lt;/ac:parameter&gt;&lt;ac:parameter ac:name="borderStyle"&gt;solid&lt;/ac:parameter&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[HOSTNAME=yourserver.suu.edu
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;h2&gt;Fifth Step&lt;/h2&gt;&lt;h5&gt;As root, run the following command:&lt;/h5&gt;&lt;ac:structured-macro ac:macro-id="d6b78a7c-5c76-450d-96ce-52c4ae561cf4" ac:name="code" ac:schema-version="1"&gt;&lt;ac:parameter ac:name="borderStyle"&gt;solid&lt;/ac:parameter&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[#echo yourserver.suu.edu &gt; /proc/sys/kernel/hostname

To verify that it worked, run:
#cat /proc/sys/kernel/hostname
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;h2&gt;Sixth Step&lt;/h2&gt;&lt;h5&gt;Red Hat - Edit the /etc/sysconfig/network-scripts/ifcfg-eth0 file&lt;/h5&gt;&lt;ac:structured-macro ac:macro-id="4918652a-99a5-4a04-9b59-d1ac59a8dff1" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[DEVICE=eth0
BOOTPROTO=static (or dhcp)
ONBOOT=yes
HWADDR=[MAC Address]
NETMASK=255.255.255.0
IPADDR=[YOURIP]
GATEWAY=[YOURGW]
Type=Ethernet]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;h5&gt;Ubuntu - Edit the /etc/network/interfaces (also /etc/network/networks with proper localnet)&lt;/h5&gt;&lt;ac:structured-macro ac:macro-id="dccb5a2d-e822-45f3-b614-93728beebe38" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet static
address 134.250.x.x
netmask 255.255.255.0
network 134.250.x.0
broadcast 134.250.x.255
gateway 134.250.x.1
dns-nameservers 134.250.2.3 134.250.6.3
dns-search suu.edu]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;h2&gt;Finally, reboot.&lt;/h2&gt;</property>
    

<property name="body">h2. First Step

h4. If IP is assigned by DHCP:
h5. Make sure /etc/hosts file looks like this:
{code:title=/etc/hosts|borderStyle=solid}
127.0.0.1     servername.suu.edu     localhost.localdomain     localhost     servername
{code}</property>
    

<property name="body">h2. First Step
h5. If IP is assigned by DHCP, make sure /etc/hosts file looks like this:
{code:title=/etc/hosts|borderStyle=solid}
127.0.0.1     servername.suu.edu     localhost.localdomain     localhost     servername
{code}
h5. If IP is hard-coded, make sure /etc/hosts file looks like this (x.x is your new IP):
{code:title=/etc/hosts|borderStyle=solid}
127.0.0.1     localhost.localdomain     localhost
134.250.x.x   yourserver.suu.edu        yourserver
{code}

h2. Second Step
h5. If you need the change to happen immediately without a reboot, run the following command as root:
{code:borderStyle=solid}
#hostname yourserver.suu.edu
{code}
h2. Third Step
h5. This step is optional, and depends on the linux distribution and version you are using.  If you have an /etc/HOSTNAME file, ensure that it is populated with a single line as follows:
{code:borderStyle=solid}
yourserver.suu.edu
{code}</property>
    

<property name="body">&lt;h1&gt;Remove unnecessary services&lt;/h1&gt;

&lt;ac:structured-macro ac:macro-id="0c279247-23f1-4c8c-a326-c38dd01228a7" ac:name="code" ac:schema-version="1"&gt;&lt;ac:parameter ac:name="borderStyle"&gt;solid&lt;/ac:parameter&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
chkconfig --del anacron
chkconfig --del autofs
chkconfig --del apmd
chkconfig --del atd
chkconfig --del gpm
chkconfig --del irda
chkconfig --del isdn
chkconfig --del netfs
chkconfig --del nfs
chkconfig --del nfslock
chkconfig --del nscd
chkconfig --del ntpd
chkconfig --del portmap
chkconfig --del sendmail
chkconfig --del smartd
chkconfig --del snmpd
chkconfig --del snmptrapd
chkconfig --del winbind
chkconfig --del ypbind
chkconfig --del avahi-daemon
chkconfig --del cups
chkconfig --del exim
chkconfig --del firstboot
chkconfig --del gpm
chkconfig --del fuse
chkconfig --del mdmonitor  --handles software raid


cd /etc/xinetd.d/
rm -rf /etc/xinetd.d/chargen*
rm -rf /etc/xinetd.d/daytime*
rm -rf /etc/xinetd.d/echo*
rm -rf /etc/xinetd.d/rsync*
rm -rf /etc/xinetd.d/time*
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;</property>
    

<property name="body">&lt;p&gt;This document pertains to Redhat Enterprise Linux specifically, but may work for other distributions as well&lt;/p&gt;

&lt;h3&gt;1- Install VNC Server&lt;/h3&gt;
&lt;p&gt;#up2date vnc-server&lt;/p&gt;

&lt;h3&gt;2- Set it to start at boot&lt;/h3&gt;
&lt;p&gt;#chkconfig vncserver on&lt;/p&gt;

&lt;h3&gt;3- Set up servers for individual users&lt;/h3&gt;
&lt;p&gt;#vi /etc/sysconfig/vncservers&lt;br /&gt;
(insert the following lines into the file)&lt;br /&gt;
VNCSERVERS=&amp;quot;1:usera 2:userb&amp;quot;   (add as many users as desired)&lt;br /&gt;
VNCSERVERARGS&lt;ac:link&gt;&lt;ri:page ri:content-title="1" /&gt;&lt;/ac:link&gt;=&amp;quot;-geometry 1280x1024&amp;quot; (set resolution you desire for user a)&lt;br /&gt;
VNCSERVERARGS&lt;ac:link&gt;&lt;ri:page ri:content-title="2" /&gt;&lt;/ac:link&gt;=&amp;quot;-geometry 1024x768&amp;quot; (set resolution you desire for user b)&lt;/p&gt;

&lt;h3&gt;4- Initialize VNC params for each user&lt;/h3&gt;
&lt;p&gt;#vncpasswd usera (enter password)&lt;br /&gt;
#vncpasswd userb (enter password)&lt;/p&gt;

&lt;h3&gt;5- Restart services&lt;/h3&gt;
&lt;p&gt;#/etc/init.d/vncserver restart&lt;/p&gt;

&lt;h3&gt;6- Edit each user's X startup script for VNC&lt;/h3&gt;
&lt;p&gt;#vi /home/usera/.vnc/xstartup&lt;br /&gt;
(the file should look like the following for full gui capability; for slow connections, there are much 'slimmer' options; this doc assumes local LAN connectivity)&lt;/p&gt;

&lt;h4&gt;# The file should look like this for a normal desktop:&lt;/h4&gt;
&lt;ac:structured-macro ac:macro-id="2217fd81-2e98-4e8e-8025-350322a48c39" ac:name="code" ac:schema-version="1"&gt;&lt;ac:parameter ac:name="title"&gt;/home/username/.vnc/xstartup&lt;/ac:parameter&gt;&lt;ac:parameter ac:name="borderStyle"&gt;solid&lt;/ac:parameter&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
#!/bin/sh
# Uncomment the following two lines for normal desktop:
unset SESSION_MANAGER
exec /etc/X11/xinit/xinitrc


The file should look like this if you have a slow connection:

#!/bin/sh

# Uncomment the following two lines for normal desktop:
# unset SESSION_MANAGER
# exec /etc/X11/xinit/xinitrc

[ -x /etc/vnc/xstartup ] &amp;&amp; exec /etc/vnc/xstartup
[ -r $HOME/.Xresources ] &amp;&amp; xrdb $HOME/.Xresources
xsetroot -solid grey
vncconfig -iconic &amp;
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &amp;
twm &amp;
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;

&lt;h3&gt;7- Restart services again&lt;/h3&gt;
&lt;p&gt;#/etc/init.d/vncserver restart&lt;/p&gt;

&lt;h3&gt;8- Connect with client from remote desktop&lt;/h3&gt;
&lt;p&gt;using the free RealVNC client, simply enter the following into the hostname prompt:&lt;br /&gt;
your.server.edu:1  (the :1 denotes user 'a' in this case; substitute other numbers accordingly)&lt;/p&gt;</property>
    

<property name="body">&lt;h3&gt;Ubuntu&lt;/h3&gt;
&lt;p&gt;Sometimes when modifying the xorg.conf file, you'll mess it up and not have a backup.  Here's a command to restore the original as it was at install.&lt;/p&gt;

&lt;p&gt;dpkg-reconfigure -phigh xserver-xorg&lt;/p&gt;</property>
    

<property name="body">&lt;h3&gt;Provided by Jeff Johnson:&lt;/h3&gt;

&lt;p&gt;No single tool, but here's what I do:&lt;/p&gt;

&lt;p&gt;0) Make a copy of everything, just in case:&lt;br /&gt;
        cd /var/lib&lt;br /&gt;
        tar czvf /tmp/rpmdb.tar.gz rpm&lt;/p&gt;

&lt;p&gt;1) Check /var/lib/rpm/Packages with db_verify.&lt;br /&gt;
        The command is&lt;br /&gt;
                db_verify /var/lib/rpm/Packages&lt;br /&gt;
        If that fails, the fix is&lt;br /&gt;
                cd /var/lib/rpm&lt;br /&gt;
                mv Packages Packages-ORIG&lt;br /&gt;
                db_dump Packages-ORIG | db_load Packages&lt;br /&gt;
        At this point Packages should be OK.&lt;/p&gt;

&lt;p&gt;2) Read all Package headers.&lt;br /&gt;
        The command is&lt;br /&gt;
                rpm -qa&lt;br /&gt;
        If that &amp;quot;works&amp;quot;, go to step 5), do &amp;quot;rpm --rebuilddb&amp;quot; and you're&lt;br /&gt;
done.&lt;br /&gt;
        If that segfaults, go to 3).&lt;br /&gt;
        if that hangs, then do&lt;br /&gt;
                rm -f /var/lib/rpm/__db*&lt;br /&gt;
        and try again.&lt;/p&gt;

&lt;p&gt;3) You have a segfault on a header.&lt;br /&gt;
        The first step is to get the segfaulting header instance.&lt;br /&gt;
        Append &amp;quot;debug&amp;quot; to the Packages configuration by&lt;br /&gt;
          echo &amp;quot;%_dbi_config_Packages %{_dbi_htconfig} lockdbfd debug&amp;quot; \&lt;br /&gt;
                &amp;gt;&amp;gt; /etc/rpm/macros&lt;/p&gt;

&lt;p&gt;        Try &amp;quot;rpm -qa&amp;quot;, lots of boring glop until segfault.&lt;/p&gt;

&lt;p&gt;        On the screen will be something like&lt;/p&gt;

&lt;p&gt;    ...&lt;br /&gt;
    Get Packages key (0x8216580,4) data (0x4014f008,155244) &amp;quot;#612&amp;quot; 47000000&lt;br /&gt;
rc&lt;br /&gt;
0kernel-enterprise-2.4.9-26beta.17&lt;br /&gt;
    Get Packages key ((nil),0) data ((nil),0) &amp;quot;&amp;quot; deadbeef rc -30990&lt;br /&gt;
    &amp;lt;segfault here&amp;gt;&lt;/p&gt;

&lt;p&gt;        The 2nd to last &amp;quot;Get Packages&amp;quot; line is what you want, the&lt;br /&gt;
        bad header instance above is &amp;quot;612&amp;quot; in decimal. Note the&lt;br /&gt;
        package name-version-release, you'll want to reinstall&lt;br /&gt;
        that package somewhen.&lt;/p&gt;

&lt;p&gt;4) Nuke the bad header.&lt;br /&gt;
        I usually whip out my handy-dandy header instance deleter,&lt;br /&gt;
        edit the bad record into the source, compile, run, and go back&lt;br /&gt;
        to step 2).&lt;/p&gt;


&lt;p&gt;        The program is at&lt;br /&gt;
                &lt;a class="external-link" href="ftp://people.redhat.com/jbj/t38454.c" rel="nofollow"&gt;ftp://people.redhat.com/jbj/t38454.c&lt;/a&gt;&lt;br /&gt;
        FWIW, the program is named after the bugzilla report that&lt;br /&gt;
        caused me to write it.&lt;/p&gt;

&lt;p&gt;        Retrieve, and edit the bad header instances into&lt;br /&gt;
                ...&lt;/p&gt;
  &lt;ac:structured-macro ac:macro-id="f67baad4-bff4-4158-8215-c4fbcee72f88" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[              int badrecs[] = {
--&gt; EDIT --&gt;            562, 566, 559, 561, 563, 560, 564,
                        -1
                };
                ...

        Compile with
                cc -o t38454 t38454.c -ldb-3.2

        Run as
                t38454 ]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;

&lt;p&gt;        Go back to step 2).&lt;/p&gt;

&lt;p&gt;5) Clean up.&lt;br /&gt;
        a) rpm --rebuilddb&lt;br /&gt;
        b) rm -f /etc/rpm/macros&lt;br /&gt;
        c) rm -rf /var/lib/rpmrebuild*&lt;br /&gt;
        d) Reinstall the deleted package.&lt;/p&gt;</property>
    

<property name="body">### This document pertains to Redhat Enterprise Linux specifically, but may work for other distributions as well

h3. 1- Install VNC Server
#up2date vnc-server

h3. 2- Set it to start at boot
#chkconfig vncserver on

h3. 3- Set up servers for individual users
#vi /etc/sysconfig/vncservers
(insert the following lines into the file)
VNCSERVERS="1:usera 2:userb"   (add as many users as desired)
VNCSERVERARGS[1]="-geometry 1280x1024" (set resolution you desire for user a)
VNCSERVERARGS[2]="-geometry 1024x768" (set resolution you desire for user b)

h3. 4- Initialize VNC params for each user
#vncpasswd usera (enter password)
#vncpasswd userb (enter password)

h3. 5- Restart services
#/etc/init.d/vncserver restart

h3. 6- Edit each user's X startup script for VNC
#vi /home/usera/.vnc/xstartup
(the file should look like the following for full gui capability; for slow connections, there are much 'slimmer' options; this doc assumes local LAN connectivity)

h4. # The file should look like this for a normal desktop:
{code:title=/home/username/.vnc/xstartup|borderStyle=solid}
#!/bin/sh
# Uncomment the following two lines for normal desktop:
unset SESSION_MANAGER
exec /etc/X11/xinit/xinitrc


The file should look like this if you have a slow connection:

#!/bin/sh

# Uncomment the following two lines for normal desktop:
# unset SESSION_MANAGER
# exec /etc/X11/xinit/xinitrc

[ -x /etc/vnc/xstartup ] &amp;&amp; exec /etc/vnc/xstartup
[ -r $HOME/.Xresources ] &amp;&amp; xrdb $HOME/.Xresources
xsetroot -solid grey
vncconfig -iconic &amp;
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &amp;
twm &amp;
{code}

h3. 7- Restart services again
#/etc/init.d/vncserver restart

h3. 8- Connect with client from remote desktop
using the free RealVNC client, simply enter the following into the hostname prompt:
your.server.edu:1  (the :1 denotes user 'a' in this case; substitute other numbers accordingly)</property>
    

<property name="body">&lt;h4&gt;The latest client for Windows and Linux can be found at ftp://archive.suu.edu/clients&lt;/h4&gt;&lt;h2&gt;Example contents of dsm.opt file and dsm.sys for Ubuntu&lt;/h2&gt;&lt;ac:structured-macro ac:macro-id="16b70af6-809b-4b29-a505-0a94b35d0c72" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[DSM.OPT:
 
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tsm
 
DSM.SYS:

************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************
*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.
*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.
************************************************************************
SErvername  tsm
   COMMMethod         TCPip
   TCPPort            1500
   TCPServeraddress   tsm.suu.edu
nodename WIKI
passwordaccess generate
MANAGEDSERVICES schedule webclient
include /home/.../*
include /etc/.../*
exclude.dir /bin
exclude.dir /boot
exclude.dir /dev
exclude.dir /initrd
exclude.dir /lib
exclude.dir /lost*
exclude.dir /media
exclude.dir /mnt
exclude.dir /opt
exclude.dir /proc
exclude.dir /root
exclude.dir /sbin
exclude.dir /srv
exclude.dir /tmp
exclude.dir /usr/bin
exclude.dir /usr/games
exclude.dir /usr/include
exclude.dir /usr/lib
exclude.dir /usr/sbin
exclude.dir /usr/share
exclude.dir /usr/src
exclude.dir /usr/X11R6
exclude.dir /usr/local/bin
exclude.dir /usr/local/games
exclude.dir /usr/local/include
exclude.dir /usr/local/lib
exclude.dir /usr/local/sbin
exclude.dir /usr/local/share
exclude.dir /usr/local/src
exclude.dir /var/lib]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;h2&gt;Configuring Automatic Startup&lt;/h2&gt;&lt;p&gt;Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:&lt;/p&gt;&lt;ac:structured-macro ac:macro-id="461cf114-8996-4419-86ea-c935309d59ea" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
#export LANG=en_US;
#export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;h4&gt;Next, execute the following commands:&lt;/h4&gt;&lt;ac:structured-macro ac:macro-id="cdeb93bb-ad7d-4f79-ba37-14e8872c7e76" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[FOR UBUNTU SERVER:

chmod 775 suu_tivoli
update-rc.d suu_tivoli defaults

FOR RED HAT:
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;h4&gt;Next, register a new node on the tsm server (only for traditional backups, NOT full VMs)&lt;/h4&gt;&lt;ac:structured-macro ac:macro-id="4a0e1641-96ae-4ea4-a9d5-d757949301ab" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[register node &lt;nodename&gt; &lt;password&gt; passe=0 do=standard url=http://&lt;host.suu.edu&gt;:1581 clo={windows|linux}]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;h4&gt;Then, configure the schedule via the GUI at&amp;nbsp;&lt;a href="https://tsm.suu.edu:16311/ibm/console"&gt;https://tsm.suu.edu:16311/ibm/console&lt;/a&gt;&lt;/h4&gt;&lt;h4&gt;Finally, you must start the daemon manually and enter the password; this is only required once- it will remember it going forward&lt;/h4&gt;&lt;p&gt;At this point, it is assumed you have talked to Matt and set up a login and password for your server. Run the following commands to initialize and run a backup:&lt;/p&gt;&lt;ac:structured-macro ac:macro-id="42d6da81-c537-4c52-be52-7ee5f993549d" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[#dsmc
It will prompt you for your nodename and password.  Once you have entered them, it will drop you at a tsm&gt; prompt.
You can then type 'backup', no quotes, and it will start an incremental backup.  If you don't want to start one right away,
just type 'quit', no quotes, and it will drop you back at the linux prompt.
To start the daemon, run the following command:

#/etc/init.d/suu_tivoli start
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;h2&gt;Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.&lt;/h2&gt;&lt;h4&gt;Error loading shared libraries&lt;/h4&gt;&lt;p&gt;If you encounter the following message while starting dsmc&lt;/p&gt;&lt;ac:structured-macro ac:macro-id="617f50f1-f035-4ff9-9af5-416e537b9985" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;p&gt;you need to add the path to the dsm binary directory to the file &lt;em&gt;/etc/ld.so.conf&lt;/em&gt;&lt;/p&gt;&lt;ac:structured-macro ac:macro-id="40d082cf-4250-4421-b6e2-c1ff9c9b473a" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[/opt/tivoli/tsm/client/api/bin
/usr/local/ibm/gsk8/lib
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;p&gt;&amp;nbsp;and then reimport the shared objects using the command&lt;/p&gt;&lt;ac:structured-macro ac:macro-id="da01ebc5-b519-4327-bc08-2d961fe898c1" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[ldconfig
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;h4&gt;English message repository not found&lt;/h4&gt;&lt;p&gt;If you get the error message&lt;/p&gt;&lt;ac:structured-macro ac:macro-id="2c527580-eeac-49a4-b908-233b10340bd2" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;p&gt;you need to create a symbolic link in &lt;em&gt;/opt/tivoli/tsm/client/ba/bin&lt;/em&gt; with&lt;/p&gt;&lt;ac:structured-macro ac:macro-id="d7ba152f-1cad-4f01-830a-49cc1b4d10e8" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/EN_US/
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;h3&gt;Resetting encryption password:&lt;/h3&gt;&lt;ac:structured-macro ac:macro-id="a85a5909-5144-4b00-89d8-009e8321b707" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[If you ever accidentally enter the wrong encryption key on initial setup, you can have it re-prompt you by doing the following:
 
# service suu_tivoli stop
# rm /etc/adsm/TSM.PWD
# service suu_tivoli start
# dsmc s /etc/inittab (or any other small file)
 
You will be prompted for nodename, and then node password.  Once you've logged in, it will prompt you about the Encryption Key, at which point you select 1, and enter the key twice.  If the backup completes successfully, you can move on to creating a full backup.]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;</property>
    

<property name="body">h2. Example contents of dsm.opt file
{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Example contents of dsm.sys file
{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMmethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu

nodename &lt;servernodename_goeshere&gt; ex. ASPEN
passwordaccess generate
MANAGEDSERVICES	schedule webclient

exclude     /.../core
exclude     /.../tmp/.../*
exclude.dir /proc
exclude.dir /proc/
exclude.dir /dev
exclude.dir /dev/
exclude.dir	/mnt
exclude.dir	/mnt/
exclude.dir /usr/share/man
exclude dsmsched.log
{code}

h2. Configuring Automatic Startup
h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:
{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}
h4. Next, execute the following commands:
{code}
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}
h4. Finally, you must start the daemon manually and enter the password; this is only required once- it will remember it going forward
At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmcad
#dsmc
{code}
Once you run dsmc, it will prompt for a username and password.  Once you have entered them, you should be at a tsm prompt.  Enter the following:
{code}
backup
{code}</property>
    

<property name="body">&lt;p&gt;CUPS Doc&lt;br /&gt;
To install cups and hplip on a new server, here is the procedure:&lt;/p&gt;

&lt;p&gt;CUPS:&lt;br /&gt;
1- ensure you have the following packages installed:&lt;br /&gt;
gcc, libjpeg, libjpeg-devel, libpng, libpng-devel, libtiff, libtiff-devel, zlib, zlib-devel,dbus-devel,php-devel,pyqt,pyqt-devel,xsane,net-snmp-devel&lt;/p&gt;

&lt;p&gt;2- Download the latest stable source from www.cups.org (1.3.6 as of this writing)&lt;/p&gt;

&lt;p&gt;3- Compile the source as follows:&lt;/p&gt;
&lt;ac:structured-macro ac:macro-id="b06961e8-28ff-4c79-b6fb-de1ac73ee21b" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
rpmbuild -ta cups-version-source.tar.gz --without dbus
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;
&lt;p&gt;This will produce several compiled rpms in the /usr/src/redhat/RPMS/i386 directory.&lt;br /&gt;
The only ones you want are cups, cups-libs, cups-debuginfo, cups-devel,cups-lpd,cups-php&lt;br /&gt;
Do an rpm -Uvh on all these packages.&lt;/p&gt;

&lt;p&gt;HPLIP:&lt;/p&gt;
&lt;ac:structured-macro ac:macro-id="4a2b5564-4c8d-4788-bea5-214bcc2e6eca" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
#tar -zxvf hplip-****.gz
#cd hplip-****
#(as banjobs, not ROOT) ./configure --enable-network-build --disable-dbus-build --disable-pp-build --disable-fax-build --disable-gui-build --disable-scan-build --enable-doc-build --enable-foomatic-ppd-install --disable-foomatic-drv-install --with-hpppddir=/usr/share/cups/model/HP --disable-hpijs-only-build --prefix=/usr
#(as banjobs, not ROOT) make
#(as ROOT) make install
#/etc/init.d/hplip restart
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;
&lt;p&gt;The following command creates a print queue called tranb on Solaris&lt;br /&gt;
lpadmin -p tranb -v/dev/null -m netstandard -o dest=134.250.51.248:3002 -T PS -I postscript -o protocol=tcp&lt;/p&gt;

&lt;p&gt;--landscape using LPR&lt;/p&gt;

&lt;p&gt;lpr  -o landscape -o cpi=15 -o lpi=12 -o cpi=16 -Pormond SHRTRTC_876.lis&lt;/p&gt;

&lt;p&gt;Cups Options:&lt;/p&gt;

&lt;p&gt;Jobs can also have options associated with them such as media size, number of copies, and priority.&lt;br /&gt;
CUPS supports collections of printers known as classes. Jobs sent to a class are forwarded to the first available printer in the class.&lt;br /&gt;
Filters allow a user or application to print many types of files without extra effort. Print jobs sent to a CUPS server are filtered before sending them to a printer.&lt;br /&gt;
Some filters convert job files to different formats that the printer can understand. Others perform page selection and ordering tasks.&lt;/p&gt;

&lt;p&gt;CUPS provides filters for printing many types of image files, HP-GL/2 files, PDF files, and text files.&lt;br /&gt;
CUPS also supplies PostScript and image file Raster Image Processor (&amp;quot;RIP&amp;quot;) filters that convert PostScript or image files into bitmaps that can be sent to a raster printer.&lt;/p&gt;

&lt;p&gt;CUPS also provides implicit classes, which are collections of printers and/or classes with the same name. This allows you to setup multiple servers pointing to the same physical network printer,&lt;br /&gt;
for example, so that you aren't relying on a single system for printing.  Because this also works with printer classes, you can setup multiple servers and printers&lt;br /&gt;
and never worry about a single point of failure unless all of the printers and servers go down!&lt;/p&gt;

&lt;p&gt;General Options&lt;/p&gt;

&lt;p&gt;The following options apply when printing all types of files.&lt;br /&gt;
Selecting the Media Size, Type, and Source&lt;/p&gt;

&lt;p&gt;The -o media=xyz option sets the media size, type, and/or source:&lt;/p&gt;

&lt;p&gt;lp -o media=Letter filename ENTER&lt;br /&gt;
lp -o media=Letter,MultiPurpose filename ENTER&lt;br /&gt;
lpr -o media=Letter,Transparency filename ENTER&lt;br /&gt;
lpr -o media=Letter,MultiPurpose,Transparency filename ENTER&lt;/p&gt;

&lt;p&gt;The available media sizes, types, and sources depend on the printer, but most support the following options (case is not significant):&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;Letter - US Letter (8.5x11 inches, or 216x279mm)&lt;/li&gt;
	&lt;li&gt;Legal - US Legal (8.5x14 inches, or 216x356mm)&lt;/li&gt;
	&lt;li&gt;A4 - ISO A4 (8.27x11.69 inches, or 210x297mm)&lt;/li&gt;
	&lt;li&gt;COM10 - US #10 Envelope (9.5x4.125 inches, or 241x105mm)&lt;/li&gt;
	&lt;li&gt;DL - ISO DL Envelope (8.66x4.33 inches, or 220x110mm)&lt;/li&gt;
	&lt;li&gt;Transparency - Transparency media type or source&lt;/li&gt;
	&lt;li&gt;Upper - Upper paper tray&lt;/li&gt;
	&lt;li&gt;Lower - Lower paper tray&lt;/li&gt;
	&lt;li&gt;MultiPurpose - Multi-purpose paper tray&lt;/li&gt;
	&lt;li&gt;LargeCapacity - Large capacity paper tray&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;The actual options supported are defined in the printer's PPD file in the PageSize, InputSlot, and MediaType options.&lt;br /&gt;
Setting the Orientation&lt;/p&gt;

&lt;p&gt;The -o landscape option will rotate the page 90 degrees to print in landscape orientation:&lt;/p&gt;

&lt;p&gt;lp -o landscape filename ENTER&lt;br /&gt;
lpr -o landscape filename ENTER&lt;/p&gt;

&lt;p&gt;Printing On Both Sides of the Paper&lt;/p&gt;

&lt;p&gt;The -o sides=two-sided-short-edge and -o sides=two-sided-long-edge options will enable duplexing on the printer, if the printer supports it. The -o sides=two-sided-short-edge option is suitable for landscape pages, while the -o sides=two-sided-long-edge option is suitable for portrait pages:&lt;/p&gt;

&lt;p&gt;lp -o sides=two-sided-short-edge filename ENTER&lt;br /&gt;
lp -o sides=two-sided-long-edge filename ENTER&lt;br /&gt;
lpr -o sides=two-sided-long-edge filename ENTER&lt;/p&gt;

&lt;p&gt;The default is to print single-sided:&lt;/p&gt;

&lt;p&gt;lp -o sides=one-sided filename ENTER&lt;br /&gt;
lpr -o sides=one-sided filename ENTER&lt;/p&gt;

&lt;p&gt;Banner Options&lt;/p&gt;

&lt;p&gt;The following options apply when printing all types of files.&lt;br /&gt;
Selecting the Banner Page(s)&lt;/p&gt;

&lt;p&gt;The -o jobsheets=start,end option sets the banner page(s) to use for a job:&lt;/p&gt;

&lt;p&gt;lp -o job-sheets=none filename ENTER&lt;br /&gt;
lp -o job-sheets=standard filename ENTER&lt;br /&gt;
lpr -o job-sheets=classified,classified filename ENTER&lt;/p&gt;

&lt;p&gt;If only one banner file is specified, it will be printed before the files in the job. If a second banner file is specified, it is printed after the files in the job.&lt;/p&gt;

&lt;p&gt;The available banner pages depend on the local system configuration; CUPS includes the following banner files:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;none - Do not produce a banner page.&lt;/li&gt;
	&lt;li&gt;classified - A banner page with a &amp;quot;classified&amp;quot; label at the top and bottom.&lt;/li&gt;
	&lt;li&gt;confidential - A banner page with a &amp;quot;confidential&amp;quot; label at the top and bottom.&lt;/li&gt;
	&lt;li&gt;secret - A banner page with a &amp;quot;secret&amp;quot; label at the top and bottom.&lt;/li&gt;
	&lt;li&gt;standard - A banner page with no label at the top and bottom.&lt;/li&gt;
	&lt;li&gt;topsecret - A banner page with a &amp;quot;top secret&amp;quot; label at the top and bottom.&lt;/li&gt;
	&lt;li&gt;unclassified - A banner page with an &amp;quot;unclassified&amp;quot; label at the top and bottom.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Document Options&lt;/p&gt;

&lt;p&gt;The following options apply when printing all types of files.&lt;br /&gt;
Selecting a Range of Pages&lt;/p&gt;

&lt;p&gt;The -o page-ranges=pages option selects a range of pages for printing:&lt;/p&gt;

&lt;p&gt;lp -o page-ranges=1 filename ENTER&lt;br /&gt;
lp -o page-ranges=1-4 filename ENTER&lt;br /&gt;
lp -o page-ranges=1-4,7,9-12 filename ENTER&lt;br /&gt;
lpr -o page-ranges=1-4,7,9-12 filename ENTER&lt;/p&gt;

&lt;p&gt;As shown above, the pages value can be a single page, a range of pages, or a collection of page numbers and ranges separated by commas. The pages will always be printed in ascending order, regardless of the order of the pages in the page-ranges option.&lt;/p&gt;

&lt;p&gt;The default is to print all pages.&lt;br /&gt;
Selecting Even or Odd Pages&lt;/p&gt;

&lt;p&gt;Use the -o page-set=set option to select the even or odd pages:&lt;/p&gt;

&lt;p&gt;lp -o page-set=odd filename ENTER&lt;br /&gt;
lp -o page-set=even filename ENTER&lt;br /&gt;
lpr -o page-set=even filename ENTER&lt;/p&gt;

&lt;p&gt;The default is to print all pages.&lt;br /&gt;
Setting the Output Order&lt;/p&gt;

&lt;p&gt;The the -o outputorder=order option to set the output order of all pages:&lt;/p&gt;

&lt;p&gt;lp -o outputorder=normal filename ENTER&lt;br /&gt;
lp -o outputorder=reverse filename ENTER&lt;br /&gt;
lpr -o outputorder=reverse filename ENTER&lt;/p&gt;

&lt;p&gt;N-Up Printing&lt;/p&gt;

&lt;p&gt;The -o number-up=value option selects N-Up printing. N-Up printing places multiple document pages on a single printed page. CUPS supports 1, 2, 4, 6, 9, and 16-Up formats; the default format is 1-Up:&lt;/p&gt;

&lt;p&gt;lp -o number-up=1 filename ENTER&lt;br /&gt;
lp -o number-up=2 filename ENTER&lt;br /&gt;
lp -o number-up=4 filename ENTER&lt;br /&gt;
lpr -o number-up=16 filename ENTER&lt;/p&gt;

&lt;p&gt;The -o page-border=value option chooses the border to draw around each page:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;-o page-border=double; draw two hairline borders around each page&lt;/li&gt;
	&lt;li&gt;-o page-border=double-thick; draw two 1pt borders around each page&lt;/li&gt;
	&lt;li&gt;-o page-border=none; do not draw a border (default)&lt;/li&gt;
	&lt;li&gt;-o page-border=single; draw one hairline border around each page&lt;/li&gt;
	&lt;li&gt;-o page-border=single-thick; draw one 1pt border around each page&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;The -o number-up-layout=value option chooses the layout of the pages on each output page:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;-o number-up-layout=btlr; Bottom to top, left to right&lt;/li&gt;
	&lt;li&gt;-o number-up-layout=btrl; Bottom to top, right to left&lt;/li&gt;
	&lt;li&gt;-o number-up-layout=lrbt; Left to right, bottom to top&lt;/li&gt;
	&lt;li&gt;-o number-up-layout=lrtb; Left to right, top to bottom (default)&lt;/li&gt;
	&lt;li&gt;-o number-up-layout=rlbt; Right to left, bottom to top&lt;/li&gt;
	&lt;li&gt;-o number-up-layout=rltb; Right to left, top to bottom&lt;/li&gt;
	&lt;li&gt;-o number-up-layout=tblr; Top to bottom, left to right&lt;/li&gt;
	&lt;li&gt;-o number-up-layout=tbrl; Top to bottom, right to left&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Mirroring Prints&lt;/p&gt;

&lt;p&gt;You can mirror a print using the -o mirror option:&lt;/p&gt;

&lt;p&gt;lp -o mirror filename ENTER&lt;br /&gt;
lpr -o mirror filename ENTER&lt;/p&gt;

&lt;p&gt;This is useful for printing mirrored pages on transfer paper, for T shirts, mugs, etc.&lt;br /&gt;
Setting the Brightness&lt;/p&gt;

&lt;p&gt;You can control the overall brightness of the printed output using the -o brightness=percent option:&lt;/p&gt;

&lt;p&gt;lp -o brightness=120 filename ENTER&lt;br /&gt;
lpr -o brightness=120 filename ENTER&lt;/p&gt;

&lt;p&gt;Values greater than 100 will lighten the print, while values less than 100 will darken it.&lt;br /&gt;
Setting the Gamma Correction&lt;/p&gt;

&lt;p&gt;You can control the overall gamma correction of the printed output using the -o gamma=value option:&lt;/p&gt;

&lt;p&gt;lp -o gamma=1700 filename ENTER&lt;br /&gt;
lpr -o gamma=1700 filename ENTER&lt;/p&gt;

&lt;p&gt;Values greater than 1000 will lighten the print, while values less than 1000 will darken it. The default gamma is 1000.&lt;br /&gt;
Text Options&lt;/p&gt;

&lt;p&gt;The following options apply when printing text files.&lt;br /&gt;
Setting the Number of Characters Per Inch&lt;/p&gt;

&lt;p&gt;The -o cpi=value option sets the number of characters per inch:&lt;/p&gt;

&lt;p&gt;lp -o cpi=10 filename ENTER&lt;br /&gt;
lp -o cpi=12 filename ENTER&lt;br /&gt;
lpr -o cpi=17 filename ENTER&lt;/p&gt;

&lt;p&gt;The default characters per inch is 10.&lt;br /&gt;
Setting the Number of Lines Per Inch&lt;/p&gt;

&lt;p&gt;The -o lpi=value option sets the number of lines per inch:&lt;/p&gt;

&lt;p&gt;lp -o lpi=6 filename ENTER&lt;br /&gt;
lpr -o lpi=8 filename ENTER&lt;/p&gt;

&lt;p&gt;The default lines per inch is 6.&lt;br /&gt;
Setting the Number of Columns&lt;/p&gt;

&lt;p&gt;The -o columns=value option sets the number of text columns:&lt;/p&gt;

&lt;p&gt;lp -o columns=2 filename ENTER&lt;br /&gt;
lpr -o columns=3 filename ENTER&lt;/p&gt;

&lt;p&gt;The default number of columns is 1.&lt;br /&gt;
Setting the Page Margins&lt;/p&gt;

&lt;p&gt;Normally the page margins are set to the hard limits of the printer. Use the -o page-left=value, -o page-right=value , -o page-top=value, and -o page-bottom=value options to adjust the page margins:&lt;/p&gt;

&lt;p&gt;lp -o page-left=value filename ENTER&lt;br /&gt;
lp -o page-right=value filename ENTER&lt;br /&gt;
lp -o page-top=value filename ENTER&lt;br /&gt;
lp -o page-bottom=value filename ENTER&lt;br /&gt;
lpr -o page-bottom=value filename ENTER&lt;/p&gt;

&lt;p&gt;The value argument is the margin in points; each point is 1/72 inch or 0.35mm.&lt;br /&gt;
Pretty Printing&lt;/p&gt;

&lt;p&gt;The -o prettyprint option puts a header at the top of each page with the page number, job title (usually the filename), and the date. Also, C and C++ keywords are highlighted, and comment lines are italicized:&lt;/p&gt;

&lt;p&gt;lp -o prettyprint filename ENTER&lt;br /&gt;
lpr -o prettyprint filename ENTER&lt;/p&gt;

&lt;p&gt;Image Options&lt;/p&gt;

&lt;p&gt;The following options apply when printing image files.&lt;br /&gt;
Positioning the Image&lt;/p&gt;

&lt;p&gt;The -o position=name option specifies the position of the image on the page:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;center - Center the image on the page (default)&lt;/li&gt;
	&lt;li&gt;top - Print the image centered at the top of the page&lt;/li&gt;
	&lt;li&gt;left - Print the image centered on the left of page&lt;/li&gt;
	&lt;li&gt;right - Print the image centered on the right of the page&lt;/li&gt;
	&lt;li&gt;top-left - Print the image at the top left corner of the page&lt;/li&gt;
	&lt;li&gt;top-right - Print the image at the top right corner of the page&lt;/li&gt;
	&lt;li&gt;bottom - Print the image centered at the bottom of the page&lt;/li&gt;
	&lt;li&gt;bottom-left - Print the image at the bottom left corner of the page&lt;/li&gt;
	&lt;li&gt;bottom-right - Print the image at the bottom right corner of the page&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Scaling the Image&lt;/p&gt;

&lt;p&gt;The -o scaling=percent, -o ppi=value, and -o natural-scaling=percent options change the size of a printed image:&lt;/p&gt;

&lt;p&gt;lp -o scaling=percent filename ENTER&lt;br /&gt;
lp -o ppi=value filename ENTER&lt;br /&gt;
lpr -o natural-scaling=percent filename ENTER&lt;/p&gt;

&lt;p&gt;The scaling=percent value is a number from 1 to 800 specifying the size in relation to the page (not the image.) A scaling of 100 percent will fill the page as completely as the image aspect ratio allows. A scaling of 200 percent will print on up to 4 pages.&lt;/p&gt;

&lt;p&gt;The ppi=value value is a number from 1 to 1200 specifying the resolution of the image in pixels per inch. An image that is 3000x2400 pixels will print 10x8 inches at 300 pixels per inch, for example. If the specified resolution makes the image larger than the page, multiple pages will be printed to satisfy the request.&lt;/p&gt;

&lt;p&gt;The natural-scaling=percent value is a number from 1 to 800 specifying the size in relation to the natural image size. A scaling of 100 percent will print the image at its natural size, while a scaling of 50 percent will print the image at half its natural size. If the specified scaling makes the image larger than the page, multiple pages will be printed to satisfy the request.&lt;br /&gt;
Adjusting the Hue (Tint) of an Image&lt;/p&gt;

&lt;p&gt;The -o hue=value option will adjust the hue of the printed image, much like the tint control on your television:&lt;/p&gt;

&lt;p&gt;lp -o hue=value filename ENTER&lt;br /&gt;
lpr -o hue=value filename ENTER&lt;/p&gt;

&lt;p&gt;The value argument is a number from -360 to 360 and represents the color hue rotation. The following table summarizes the change you'll see with different colors:&lt;br /&gt;
Original	hue=-45	hue=45&lt;br /&gt;
Red	Purple	Yellow-orange&lt;br /&gt;
Green	Yellow-green	Blue-green&lt;br /&gt;
Yellow	Orange	Green-yellow&lt;br /&gt;
Blue	Sky-blue	Purple&lt;br /&gt;
Magenta	Indigo	Crimson&lt;br /&gt;
Cyan	Blue-green	Light-navy-blue&lt;/p&gt;

&lt;p&gt;The default hue adjustment is 0.&lt;br /&gt;
Adjusting the Saturation (Color) of an Image&lt;/p&gt;

&lt;p&gt;The -o saturation=percent option adjusts the saturation of the colors in an image, much like the color knob on your television:&lt;/p&gt;

&lt;p&gt;lp -o saturation=percent filename ENTER&lt;br /&gt;
lpr -o saturation=percent filename ENTER&lt;/p&gt;

&lt;p&gt;The percent argument specifies the color saturation from 0 to 200. A color saturation of 0 produces a black-and-white print, while a value of 200 will make the colors extremely intense.&lt;/p&gt;

&lt;p&gt;The default saturation is 100.&lt;br /&gt;
HP-GL/2 Options&lt;/p&gt;

&lt;p&gt;The following options apply to HP-GL/2 files.&lt;br /&gt;
Printing in Black&lt;/p&gt;

&lt;p&gt;The -o blackplot option specifies that all pens should plot in black:&lt;/p&gt;

&lt;p&gt;lp -o blackplot filename ENTER&lt;br /&gt;
lpr -o blackplot filename ENTER&lt;/p&gt;

&lt;p&gt;The default is to use the colors defined in the plot file or the standard pen colors defined in the HP-GL/2 reference manual from Hewlett Packard.&lt;br /&gt;
Fitting the Plot on the Page&lt;/p&gt;

&lt;p&gt;The -o fitplot option specifies that the plot should be scaled to fit on the page:&lt;/p&gt;

&lt;p&gt;lp -o fitplot filename ENTER&lt;br /&gt;
lpr -o fitplot filename ENTER&lt;/p&gt;

&lt;p&gt;The default is to use the absolute distances specified in the plot file.&lt;br /&gt;
NOTE:&lt;/p&gt;

&lt;p&gt;This feature depends upon an accurate plot size (PS) command in the HP-GL/2 file. If no plot size is given in the file than the HP-GL/2 filter assumes the plot is ANSI E size.&lt;/p&gt;

&lt;p&gt;Setting the Default Pen Width&lt;/p&gt;

&lt;p&gt;The -o penwidth=value option specifies the default pen width for HP-GL/2 files:&lt;/p&gt;

&lt;p&gt;lp -o penwidth=value filename ENTER&lt;br /&gt;
lpr -o penwidth=value filename ENTER&lt;/p&gt;

&lt;p&gt;The pen width value specifies the pen width in micrometers. The default value of 1000 produces lines that are 1 millimeter in width. Specifying a pen width of 0 produces lines that are exactly 1 pixel wide.&lt;br /&gt;
NOTE:&lt;/p&gt;

&lt;p&gt;This option is ignored when the pen widths are set in the plot file.&lt;/p&gt;

&lt;p&gt;Raw or Unfiltered Output&lt;/p&gt;

&lt;p&gt;The -o raw option allows you to send files directly to a printer without filtering. This is sometimes required when printing from applications that provide their own &amp;quot;printer drivers&amp;quot; for your printer:&lt;/p&gt;

&lt;p&gt;lp -o raw filename ENTER&lt;br /&gt;
lpr -o raw filename ENTER&lt;/p&gt;

&lt;p&gt;The -l option can also be used with the lpr command to send files directly to a printer:&lt;/p&gt;

&lt;p&gt;lpr -l filename ENTER&lt;/p&gt;

&lt;p&gt;4 - Saving Printer Options and Defaults&lt;/p&gt;

&lt;p&gt;This chapter describes how to save printer options for your printer and set your own default printer.&lt;br /&gt;
Printer Options&lt;/p&gt;

&lt;p&gt;Each printer supports a large number of options, which you learned about in Chapter 3, &amp;quot;Standard Printer Options&amp;quot;. Rather than specifying these options each time you print a file, CUPS allows you to save them as &amp;quot;default&amp;quot; options for the printer.&lt;/p&gt;

&lt;p&gt;The lpoptions(1) command saves the options for your printers. Like the lp and lpr commands, it accepts printer options using the -o argument:&lt;/p&gt;

&lt;p&gt;lpoptions -o prettyprint ENTER&lt;br /&gt;
lpoptions -o media=A4 -o sides=two-sided-long-edge ENTER&lt;br /&gt;
lpoptions -o media=Legal -o scaling=100 ENTER&lt;/p&gt;

&lt;p&gt;Once saved, any lp or lpr command will use them when you print.&lt;br /&gt;
Note:&lt;/p&gt;

&lt;p&gt;Running the lpoptions command as the root user (or any user with a UID of 0) will set the default options for all users. The root account does not have its own set of default options.&lt;/p&gt;

&lt;p&gt;Setting Options for a Specific Printer&lt;/p&gt;

&lt;p&gt;The previous example shows how to set the options for the default printer. The -p printer option specifies the options are for another printer:&lt;/p&gt;

&lt;p&gt;lpoptions -p laserjet -o prettyprint ENTER&lt;br /&gt;
lpoptions -p laserjet -o media=A4 -o sides=two-sided-long-edge ENTER&lt;br /&gt;
lpoptions -p deskjet -o media=Legal -o scaling=100 ENTER&lt;/p&gt;

&lt;p&gt;Removing Options&lt;/p&gt;

&lt;p&gt;The previous two examples shows how to set options for the default and a specific printer. Below, shows you how to remove the saved option using the -r argument:&lt;/p&gt;

&lt;p&gt;lpoptions -r prettyprint ENTER&lt;br /&gt;
lpoptions -p laserjet -r prettyprint ENTER&lt;/p&gt;

&lt;p&gt;Viewing the Current Defaults&lt;/p&gt;

&lt;p&gt;The lpoptions command can also be used to show the current options by not specifying any new options on the command-line:&lt;/p&gt;

&lt;p&gt;lpoptions ENTER&lt;br /&gt;
media=A4 sides=two-sided-long-edge&lt;br /&gt;
lpoptions -p deskjet ENTER&lt;br /&gt;
media=Legal scaling=100&lt;/p&gt;

&lt;p&gt;Viewing Options for a Specific Printer&lt;/p&gt;

&lt;p&gt;You can display the supported options using the lpoptions command with the -l option, as follows:&lt;/p&gt;

&lt;p&gt;lpoptions -p laserjet -l ENTER&lt;/p&gt;

&lt;p&gt;Setting the Default Printer&lt;/p&gt;

&lt;p&gt;The administrator normally will set a system-wide default printer that is normally used as the default printer by everyone. Use the -d printer option to set your own default printer:&lt;/p&gt;

&lt;p&gt;lpoptions -d deskjet ENTER&lt;/p&gt;

&lt;p&gt;The printer can be local (deskjet) or remote ( deskjet@server).&lt;br /&gt;
Printer Instances&lt;/p&gt;

&lt;p&gt;Besides setting options for each print queue, CUPS supports printer instances which allow you to define several different sets of options for each printer. You specify a printer instance using the slash &lt;ac:emoticon ac:name="tick" /&gt; character:&lt;/p&gt;

&lt;p&gt;lpoptions -p laserjet/duplex -o sides=two-sided-long-edge ENTER&lt;br /&gt;
lpoptions -p laserjet/legal -o media=Legal ENTER&lt;/p&gt;

&lt;p&gt;The lp and lpr commands also understand this notation:&lt;/p&gt;

&lt;p&gt;lp -d laserjet/duplex filename ENTER&lt;br /&gt;
lpr -P laserjet/legal filename ENTER&lt;/p&gt;

&lt;p&gt;Removing Instances&lt;/p&gt;

&lt;p&gt;Use the -x printer/instance option to remove a printer instance that you no longer need:&lt;/p&gt;

&lt;p&gt;lpoptions -x laserjet ENTER&lt;br /&gt;
lpoptions -x laserjet/duplex ENTER&lt;br /&gt;
lpoptions -x laserjet/legal ENTER&lt;/p&gt;

&lt;p&gt;The -x option only removes the default options for that printer and instance; the original print queue will remain until deleted with the lpadmin(8) command by the administrator.&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;Allow printing to printer MyLaserJet from&lt;/li&gt;
	&lt;li&gt;itself and computers 192.10.2.5 and 192.10.2.6&lt;br /&gt;
&amp;lt;Location /printers/MyLaserJet&amp;gt;&lt;br /&gt;
...&lt;br /&gt;
Order deny,allow&lt;br /&gt;
Deny from all&lt;br /&gt;
Allow from 127.0.0.1&lt;br /&gt;
Allow from 192.10.2.5&lt;br /&gt;
Allow from 192.10.2.6&lt;br /&gt;
&amp;lt;/Location&amp;gt;&lt;/li&gt;
&lt;/ol&gt;


&lt;ol&gt;
	&lt;li&gt;Allow printing to printer MyLaserJet from&lt;/li&gt;
	&lt;li&gt;itself and all computers on subnet 192.10.2.x&lt;br /&gt;
&amp;lt;Location /printers/MyLaserJet&amp;gt;&lt;br /&gt;
...&lt;br /&gt;
Order deny,allow&lt;br /&gt;
Deny from all&lt;br /&gt;
Allow from 127.0.0.1&lt;br /&gt;
Allow from 192.10.2.0/255.255.255.0&lt;br /&gt;
&amp;lt;/Location&amp;gt;&lt;/li&gt;
&lt;/ol&gt;
</property>
    

<property name="body">CUPS Doc
To install cups and hplip on a new server, here is the procedure:

CUPS:
1- ensure you have the following packages installed:
gcc, libjpeg, libjpeg-devel, libpng, libpng-devel, libtiff, libtiff-devel, zlib, zlib-devel,dbus-devel,php-devel,pyqt,pyqt-devel,xsane

2- Download the latest stable source from www.cups.org (1.3.6 as of this writing)

3- Compile the source as follows:
{code}rpmbuild -ta cups-version-source.tar.gz{code}

This will produce several compiled rpms in the /usr/src/redhat/RPMS/i386 directory.
The only ones you want are cups, cups-libs, cups-debuginfo, cups-devel,cups-lpd,cups-php
Do an rpm -Uvh on all these packages.

HPLIP:
{code}#tar -zxvf hplip-****.gz
#cd hplip-****
#(as banjobs, not ROOT) ./configure --enable-network-build --disable-pp-build --disable-fax-build --disable-gui-build --disable-scan-build --enable-doc-build --enable-foomatic-ppd-install --disable-foomatic-drv-install --with-hpppddir=/usr/share/cups/model/HP --disable-hpijs-only-build --prefix=/usr
#(as banjobs, not ROOT) make
#(as ROOT) make install
#/etc/init.d/hplip restart 
{code}
Cups Options:

Jobs can also have options associated with them such as media size, number of copies, and priority.
CUPS supports collections of printers known as classes. Jobs sent to a class are forwarded to the first available printer in the class.
Filters allow a user or application to print many types of files without extra effort. Print jobs sent to a CUPS server are filtered before sending them to a printer.
 Some filters convert job files to different formats that the printer can understand. Others perform page selection and ordering tasks.

CUPS provides filters for printing many types of image files, HP-GL/2 files, PDF files, and text files.
 CUPS also supplies PostScript and image file Raster Image Processor ("RIP") filters that convert PostScript or image files into bitmaps that can be sent to a raster printer.
 
 
 CUPS also provides implicit classes, which are collections of printers and/or classes with the same name. This allows you to setup multiple servers pointing to the same physical network printer, 
 for example, so that you aren't relying on a single system for printing.  Because this also works with printer classes, you can setup multiple servers and printers
  and never worry about a single point of failure unless all of the printers and servers go down!
  
  General Options

The following options apply when printing all types of files.
Selecting the Media Size, Type, and Source

The -o media=xyz option sets the media size, type, and/or source:

      lp -o media=Letter filename ENTER
      lp -o media=Letter,MultiPurpose filename ENTER
      lpr -o media=Letter,Transparency filename ENTER
      lpr -o media=Letter,MultiPurpose,Transparency filename ENTER

The available media sizes, types, and sources depend on the printer, but most support the following options (case is not significant):

    * Letter - US Letter (8.5x11 inches, or 216x279mm)
    * Legal - US Legal (8.5x14 inches, or 216x356mm)
    * A4 - ISO A4 (8.27x11.69 inches, or 210x297mm)
    * COM10 - US #10 Envelope (9.5x4.125 inches, or 241x105mm)
    * DL - ISO DL Envelope (8.66x4.33 inches, or 220x110mm)
    * Transparency - Transparency media type or source
    * Upper - Upper paper tray
    * Lower - Lower paper tray
    * MultiPurpose - Multi-purpose paper tray
    * LargeCapacity - Large capacity paper tray

The actual options supported are defined in the printer's PPD file in the PageSize, InputSlot, and MediaType options.
Setting the Orientation

The -o landscape option will rotate the page 90 degrees to print in landscape orientation:

      lp -o landscape filename ENTER
      lpr -o landscape filename ENTER

Printing On Both Sides of the Paper

The -o sides=two-sided-short-edge and -o sides=two-sided-long-edge options will enable duplexing on the printer, if the printer supports it. The -o sides=two-sided-short-edge option is suitable for landscape pages, while the -o sides=two-sided-long-edge option is suitable for portrait pages:

      lp -o sides=two-sided-short-edge filename ENTER
      lp -o sides=two-sided-long-edge filename ENTER
      lpr -o sides=two-sided-long-edge filename ENTER

The default is to print single-sided:

      lp -o sides=one-sided filename ENTER
      lpr -o sides=one-sided filename ENTER

Banner Options

The following options apply when printing all types of files.
Selecting the Banner Page(s)

The -o jobsheets=start,end option sets the banner page(s) to use for a job:

      lp -o job-sheets=none filename ENTER
      lp -o job-sheets=standard filename ENTER
      lpr -o job-sheets=classified,classified filename ENTER

If only one banner file is specified, it will be printed before the files in the job. If a second banner file is specified, it is printed after the files in the job.

The available banner pages depend on the local system configuration; CUPS includes the following banner files:

    * none - Do not produce a banner page.
    * classified - A banner page with a "classified" label at the top and bottom.
    * confidential - A banner page with a "confidential" label at the top and bottom.
    * secret - A banner page with a "secret" label at the top and bottom.
    * standard - A banner page with no label at the top and bottom.
    * topsecret - A banner page with a "top secret" label at the top and bottom.
    * unclassified - A banner page with an "unclassified" label at the top and bottom.

Document Options

The following options apply when printing all types of files.
Selecting a Range of Pages

The -o page-ranges=pages option selects a range of pages for printing:

      lp -o page-ranges=1 filename ENTER
      lp -o page-ranges=1-4 filename ENTER
      lp -o page-ranges=1-4,7,9-12 filename ENTER
      lpr -o page-ranges=1-4,7,9-12 filename ENTER

As shown above, the pages value can be a single page, a range of pages, or a collection of page numbers and ranges separated by commas. The pages will always be printed in ascending order, regardless of the order of the pages in the page-ranges option.

The default is to print all pages.
Selecting Even or Odd Pages

Use the -o page-set=set option to select the even or odd pages:

      lp -o page-set=odd filename ENTER
      lp -o page-set=even filename ENTER
      lpr -o page-set=even filename ENTER

The default is to print all pages.
Setting the Output Order

The the -o outputorder=order option to set the output order of all pages:

      lp -o outputorder=normal filename ENTER
      lp -o outputorder=reverse filename ENTER
      lpr -o outputorder=reverse filename ENTER

N-Up Printing

The -o number-up=value option selects N-Up printing. N-Up printing places multiple document pages on a single printed page. CUPS supports 1, 2, 4, 6, 9, and 16-Up formats; the default format is 1-Up:

      lp -o number-up=1 filename ENTER
      lp -o number-up=2 filename ENTER
      lp -o number-up=4 filename ENTER
      lpr -o number-up=16 filename ENTER

The -o page-border=value option chooses the border to draw around each page:

    * -o page-border=double; draw two hairline borders around each page
    * -o page-border=double-thick; draw two 1pt borders around each page
    * -o page-border=none; do not draw a border (default)
    * -o page-border=single; draw one hairline border around each page
    * -o page-border=single-thick; draw one 1pt border around each page

The -o number-up-layout=value option chooses the layout of the pages on each output page:

    * -o number-up-layout=btlr; Bottom to top, left to right
    * -o number-up-layout=btrl; Bottom to top, right to left
    * -o number-up-layout=lrbt; Left to right, bottom to top
    * -o number-up-layout=lrtb; Left to right, top to bottom (default)
    * -o number-up-layout=rlbt; Right to left, bottom to top
    * -o number-up-layout=rltb; Right to left, top to bottom
    * -o number-up-layout=tblr; Top to bottom, left to right
    * -o number-up-layout=tbrl; Top to bottom, right to left

Mirroring Prints

You can mirror a print using the -o mirror option:

      lp -o mirror filename ENTER
      lpr -o mirror filename ENTER

This is useful for printing mirrored pages on transfer paper, for T shirts, mugs, etc.
Setting the Brightness

You can control the overall brightness of the printed output using the -o brightness=percent option:

      lp -o brightness=120 filename ENTER
      lpr -o brightness=120 filename ENTER

Values greater than 100 will lighten the print, while values less than 100 will darken it.
Setting the Gamma Correction

You can control the overall gamma correction of the printed output using the -o gamma=value option:

      lp -o gamma=1700 filename ENTER
      lpr -o gamma=1700 filename ENTER

Values greater than 1000 will lighten the print, while values less than 1000 will darken it. The default gamma is 1000.
Text Options

The following options apply when printing text files.
Setting the Number of Characters Per Inch

The -o cpi=value option sets the number of characters per inch:

      lp -o cpi=10 filename ENTER
      lp -o cpi=12 filename ENTER
      lpr -o cpi=17 filename ENTER

The default characters per inch is 10.
Setting the Number of Lines Per Inch

The -o lpi=value option sets the number of lines per inch:

      lp -o lpi=6 filename ENTER
      lpr -o lpi=8 filename ENTER

The default lines per inch is 6.
Setting the Number of Columns

The -o columns=value option sets the number of text columns:

      lp -o columns=2 filename ENTER
      lpr -o columns=3 filename ENTER

The default number of columns is 1.
Setting the Page Margins

Normally the page margins are set to the hard limits of the printer. Use the -o page-left=value, -o page-right=value , -o page-top=value, and -o page-bottom=value options to adjust the page margins:

      lp -o page-left=value filename ENTER
      lp -o page-right=value filename ENTER
      lp -o page-top=value filename ENTER
      lp -o page-bottom=value filename ENTER
      lpr -o page-bottom=value filename ENTER

The value argument is the margin in points; each point is 1/72 inch or 0.35mm.
Pretty Printing

The -o prettyprint option puts a header at the top of each page with the page number, job title (usually the filename), and the date. Also, C and C++ keywords are highlighted, and comment lines are italicized:

      lp -o prettyprint filename ENTER
      lpr -o prettyprint filename ENTER

Image Options

The following options apply when printing image files.
Positioning the Image

The -o position=name option specifies the position of the image on the page:

    * center - Center the image on the page (default)
    * top - Print the image centered at the top of the page
    * left - Print the image centered on the left of page
    * right - Print the image centered on the right of the page
    * top-left - Print the image at the top left corner of the page
    * top-right - Print the image at the top right corner of the page
    * bottom - Print the image centered at the bottom of the page
    * bottom-left - Print the image at the bottom left corner of the page
    * bottom-right - Print the image at the bottom right corner of the page

Scaling the Image

The -o scaling=percent, -o ppi=value, and -o natural-scaling=percent options change the size of a printed image:

      lp -o scaling=percent filename ENTER
      lp -o ppi=value filename ENTER
      lpr -o natural-scaling=percent filename ENTER

The scaling=percent value is a number from 1 to 800 specifying the size in relation to the page (not the image.) A scaling of 100 percent will fill the page as completely as the image aspect ratio allows. A scaling of 200 percent will print on up to 4 pages.

The ppi=value value is a number from 1 to 1200 specifying the resolution of the image in pixels per inch. An image that is 3000x2400 pixels will print 10x8 inches at 300 pixels per inch, for example. If the specified resolution makes the image larger than the page, multiple pages will be printed to satisfy the request.

The natural-scaling=percent value is a number from 1 to 800 specifying the size in relation to the natural image size. A scaling of 100 percent will print the image at its natural size, while a scaling of 50 percent will print the image at half its natural size. If the specified scaling makes the image larger than the page, multiple pages will be printed to satisfy the request.
Adjusting the Hue (Tint) of an Image

The -o hue=value option will adjust the hue of the printed image, much like the tint control on your television:

      lp -o hue=value filename ENTER
      lpr -o hue=value filename ENTER

The value argument is a number from -360 to 360 and represents the color hue rotation. The following table summarizes the change you'll see with different colors:
Original	hue=-45	hue=45
Red	Purple	Yellow-orange
Green	Yellow-green	Blue-green
Yellow	Orange	Green-yellow
Blue	Sky-blue	Purple
Magenta	Indigo	Crimson
Cyan	Blue-green	Light-navy-blue

The default hue adjustment is 0.
Adjusting the Saturation (Color) of an Image

The -o saturation=percent option adjusts the saturation of the colors in an image, much like the color knob on your television:

      lp -o saturation=percent filename ENTER
      lpr -o saturation=percent filename ENTER

The percent argument specifies the color saturation from 0 to 200. A color saturation of 0 produces a black-and-white print, while a value of 200 will make the colors extremely intense.

The default saturation is 100.
HP-GL/2 Options

The following options apply to HP-GL/2 files.
Printing in Black

The -o blackplot option specifies that all pens should plot in black:

      lp -o blackplot filename ENTER
      lpr -o blackplot filename ENTER

The default is to use the colors defined in the plot file or the standard pen colors defined in the HP-GL/2 reference manual from Hewlett Packard.
Fitting the Plot on the Page

The -o fitplot option specifies that the plot should be scaled to fit on the page:

      lp -o fitplot filename ENTER
      lpr -o fitplot filename ENTER

The default is to use the absolute distances specified in the plot file.
NOTE:

This feature depends upon an accurate plot size (PS) command in the HP-GL/2 file. If no plot size is given in the file than the HP-GL/2 filter assumes the plot is ANSI E size.

Setting the Default Pen Width

The -o penwidth=value option specifies the default pen width for HP-GL/2 files:

      lp -o penwidth=value filename ENTER
      lpr -o penwidth=value filename ENTER

The pen width value specifies the pen width in micrometers. The default value of 1000 produces lines that are 1 millimeter in width. Specifying a pen width of 0 produces lines that are exactly 1 pixel wide.
NOTE:

This option is ignored when the pen widths are set in the plot file.

Raw or Unfiltered Output

The -o raw option allows you to send files directly to a printer without filtering. This is sometimes required when printing from applications that provide their own "printer drivers" for your printer:

      lp -o raw filename ENTER
      lpr -o raw filename ENTER

The -l option can also be used with the lpr command to send files directly to a printer:

      lpr -l filename ENTER

4 - Saving Printer Options and Defaults

This chapter describes how to save printer options for your printer and set your own default printer.
Printer Options

Each printer supports a large number of options, which you learned about in Chapter 3, "Standard Printer Options". Rather than specifying these options each time you print a file, CUPS allows you to save them as "default" options for the printer.

The lpoptions(1) command saves the options for your printers. Like the lp and lpr commands, it accepts printer options using the -o argument:

      lpoptions -o prettyprint ENTER
      lpoptions -o media=A4 -o sides=two-sided-long-edge ENTER
      lpoptions -o media=Legal -o scaling=100 ENTER

Once saved, any lp or lpr command will use them when you print.
Note:

Running the lpoptions command as the root user (or any user with a UID of 0) will set the default options for all users. The root account does not have its own set of default options.

Setting Options for a Specific Printer

The previous example shows how to set the options for the default printer. The -p printer option specifies the options are for another printer:

      lpoptions -p laserjet -o prettyprint ENTER
      lpoptions -p laserjet -o media=A4 -o sides=two-sided-long-edge ENTER
      lpoptions -p deskjet -o media=Legal -o scaling=100 ENTER

Removing Options

The previous two examples shows how to set options for the default and a specific printer. Below, shows you how to remove the saved option using the -r argument:

      lpoptions -r prettyprint ENTER
      lpoptions -p laserjet -r prettyprint ENTER

Viewing the Current Defaults

The lpoptions command can also be used to show the current options by not specifying any new options on the command-line:

      lpoptions ENTER
      media=A4 sides=two-sided-long-edge
      lpoptions -p deskjet ENTER
      media=Legal scaling=100

Viewing Options for a Specific Printer

You can display the supported options using the lpoptions command with the -l option, as follows:

      lpoptions -p laserjet -l ENTER

Setting the Default Printer

The administrator normally will set a system-wide default printer that is normally used as the default printer by everyone. Use the -d printer option to set your own default printer:

      lpoptions -d deskjet ENTER

The printer can be local (deskjet) or remote ( deskjet@server).
Printer Instances

Besides setting options for each print queue, CUPS supports printer instances which allow you to define several different sets of options for each printer. You specify a printer instance using the slash (/) character:

      lpoptions -p laserjet/duplex -o sides=two-sided-long-edge ENTER
      lpoptions -p laserjet/legal -o media=Legal ENTER

The lp and lpr commands also understand this notation:

      lp -d laserjet/duplex filename ENTER
      lpr -P laserjet/legal filename ENTER

Removing Instances

Use the -x printer/instance option to remove a printer instance that you no longer need:

      lpoptions -x laserjet ENTER
      lpoptions -x laserjet/duplex ENTER
      lpoptions -x laserjet/legal ENTER

The -x option only removes the default options for that printer and instance; the original print queue will remain until deleted with the lpadmin(8) command by the administrator.


# Allow printing to printer MyLaserJet from 
#    itself and computers 192.10.2.5 and 192.10.2.6
&lt;Location /printers/MyLaserJet&gt;
...
Order deny,allow
Deny from all
Allow from 127.0.0.1
Allow from 192.10.2.5
Allow from 192.10.2.6
&lt;/Location&gt;

# Allow printing to printer MyLaserJet from 
#    itself and all computers on subnet 192.10.2.x
&lt;Location /printers/MyLaserJet&gt;
...
Order deny,allow
Deny from all
Allow from 127.0.0.1
Allow from 192.10.2.0/255.255.255.0
&lt;/Location&gt;</property>
    

<property name="body">&lt;h3&gt;Bash Template for Oracle/Crystal server on Linux:&lt;/h3&gt;
&lt;ac:structured-macro ac:macro-id="46fbaff9-42ea-4305-8082-0cf9808b40f5" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
# .bash_profile

# Get the aliases and functions
if [ -f ~/.bashrc ]; then
	. ~/.bashrc
fi
CRYSTALDIR=/usr/local/CE10/crystal; export CRYSTALDIR
# User specific environment and startup programs
TOM=/usr/jakarta-tomcat-5.0.28; export TOM
JAVA_HOME=/usr/java/j2sdk1.4.2_05; export JAVA_HOME
CATALINA_HOME=/usr/jakarta-tomcat-5.0.28; export CATALINA_HOME
TWO_TASK=DEV; export TWO_TASK
LD_ASSUME_KERNEL=2.4.1; export LD_ASSUME_KERNEL
ORACLE_BASE=/opt/oracle; export ORACLE_BASE
ORACLE_HOME=/opt/oracle/product/9.2.0; export ORACLE_HOME
ORACLE_SID=DEV; export ORACLE_SID
ORACLE_OWNER=oracle; export ORACLE_OWNER
SH_LIB_PATH=$ORACLE_HOME/lib; export SH_LIB_PATH
TNS_ADMIN=$ORACLE_HOME/network/admin; export TNS_ADMIN
ORACLE_TERM=xterm; export ORACLE_TERM
CLASSPATH=/opt/oracle/product/9.2.0/jdbc/lib/classes111.zip:/usr/local/CE10/crystal/enterprise/java/applications/cewcanative.jar; export CLASSPATH
NLS_LANG=AMERICAN; export NLS_LANG
ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data; export ORA_NLS33
LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib; export LD_LIBRARY_PATH
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib; export LD_LIBRARY_PATH
PATH=$PATH:$ORACLE_HOME/bin:$HOME/bin:/usr/java/j2sdk1.4.2_05/bin
#BASEDIR=$TOM; export BASEDIR
export PATH
unset USERNAME
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;</property>
    

<property name="body">&lt;h2&gt;This document assumes you have the ncpmount, ncp, ncplogin, ncpmap, and ncpumount utilities installed on your machine&lt;/h2&gt;
&lt;ac:structured-macro ac:macro-id="b757535c-ac42-4b39-a20d-57db97d03e25" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
ncpmount -S cl01-adusers-server -A 134.250.12.107 -U username.it.administration.suu -V adusers/IT/Yourdir /dir/where/youwantitmountedonlocalfilesystem
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;</property>
    

<property name="body">&lt;p&gt;SQUID INSTALLATION:&lt;br /&gt;
Sent subscribe request to squid-users-subscribe@squid-cache.org&lt;/p&gt;

&lt;p&gt;#Fix open files limit - added the following to /etc/security/limits.conf&lt;/p&gt;

&lt;p&gt;squid soft nofile 4096&lt;br /&gt;
squid hard nofile 63536&lt;/p&gt;

&lt;p&gt;#Added the following line to /usr/include/bits/types.h file:&lt;br /&gt;
#define _ _FD_SETSIZE    8192&lt;/p&gt;

&lt;p&gt;#Ran the following as root; these will need to be executed before squid start; we will&lt;br /&gt;
stick them in the rc.d script:&lt;br /&gt;
ulimit -Hn 8192&lt;br /&gt;
echo &amp;quot;1024 61000&amp;quot; &amp;gt; /proc/sys/net/ipv4/ip_local_port_range&lt;/p&gt;

&lt;p&gt;Configure command:&lt;br /&gt;
./configure --prefix=/usr/local/squid --localstatedir=/squidcache/var --sysconfdir=/etc --enable-useragent-log --enable-icmp --enable-delay-pools --enable-htcp&lt;br /&gt;
 --enable-referer-log --enable-snmp --enable-cachemgr-hostname=squidcache.suu.edu --enable-ssl --with-openssl=/usr/local/ssl --enable-cache-digests --disable-http-violations&lt;/p&gt;
</property>
    

<property name="body">h1. The latest client for Windows and Linux can be found on the isengard FTP server in the Tivoli\Linux or Tivoli\Windoze directory

h2. Example contents of dsm.opt file
{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Example contents of dsm.sys file
{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMmethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu

nodename &lt;servernodename_goeshere&gt; ex. ASPEN
passwordaccess generate
MANAGEDSERVICES	schedule webclient

exclude     /.../core
exclude     /.../tmp/.../*
exclude.dir /proc
exclude.dir /proc/
exclude.dir /dev
exclude.dir /dev/
exclude.dir	/mnt
exclude.dir	/mnt/
exclude.dir /usr/share/man
exclude dsmsched.log
{code}

h2. Configuring Automatic Startup
h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:
{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}
h4. Next, execute the following commands:
{code}
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}
h4. Finally, you must start the daemon manually and enter the password; this is only required once- it will remember it going forward
At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmcad
#dsmc
{code}
Once you run dsmc, it will prompt for a username and password.  Once you have entered them, you should be at a tsm prompt.  Enter the following:
{code}
backup
{code}</property>
    

<property name="body">&lt;ac:structured-macro ac:macro-id="f12160db-0d69-495f-8b05-318631853549" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[The key to creating self-signed certificates in Tomcat is to remember the key files/components involved:
&lt;yourkeystore&gt; and cacerts, and an existing Java HOME variable.


&lt;yourkeystore&gt; will be whatever you decide to call it when creating the self-signed certificate.  For example, the following
command creates a keystore called mykeystore with an alias of tomcat and a validity of 10 years in the C:\ssl directory:

%JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA -keystore C:\ssl\mykeystore -validity 3650
remember first and last name must be the host+domain, i.e. tntrans.suu.edu

Export it:
%JAVA_HOME%\bin\keytool -export -alias tomcat -file D:\ssl\exported.cert -keystore C:\ssl\mykeystore

Once created, then you must import it into your existing CACERTS file for it to be 'trusted':

%JAVA_HOME%\bin\keytool -import -alias tomcat -trustcacerts -file D:\SSL\exported.cert -keystore %JAVA_HOME%\jre\lib\security\cacerts (this pass will be changeit)
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;
&lt;p&gt;&lt;span style="color: rgb(51,51,51);"&gt;Installing your Certificate with Jakarta-Tomcat.&lt;/span&gt;&lt;br /&gt;
&lt;span style="color: rgb(51,51,51);"&gt;(For Linux &amp;amp; Windows)&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;table&gt;&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;p&gt; &lt;span style="color: rgb(51,51,51);"&gt;This document explains how to generate and install a Server Digital Certificate, and answers any question you might have.&lt;/span&gt; &lt;/p&gt;&lt;/td&gt;
&lt;th&gt;&lt;p&gt; &lt;span style="color: rgb(51,51,51);"&gt;&lt;strong&gt;Creating a Certificate Signing Request&lt;/strong&gt;&lt;/span&gt;&lt;br class="atl-forced-newline" /&gt; &lt;/p&gt;&lt;/th&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;p&gt; &lt;span style="color: rgb(51,51,51);"&gt;1. Generate a private key with the following command:&lt;/span&gt;&lt;br class="atl-forced-newline" /&gt;  &lt;span style="color: rgb(51,51,51);"&gt;&lt;strong&gt;$JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA -keysize 1024 -validity 730 -keystore /path/to/domainname.kdb&lt;/strong&gt;&lt;/span&gt;&lt;br class="atl-forced-newline" /&gt;  &lt;br class="atl-forced-newline" /&gt; &lt;span style="color: rgb(51,51,51);"&gt;You will be prompted for a password. Tomcat uses a default password of &amp;quot;changeit&amp;quot; - do NOT use that. If you use a different password, you will need to specify a custom password in the server.xml configuration file.&lt;/span&gt;&lt;br class="atl-forced-newline" /&gt;  &lt;br class="atl-forced-newline" /&gt; &lt;span style="color: rgb(51,51,51);"&gt;In the next field you will be asked &amp;quot;What is your first and last name?&amp;quot; At this prompt, you must specify the common name (FQDN) of your web site.&lt;/span&gt;&lt;br class="atl-forced-newline" /&gt;  &lt;span style="color: rgb(51,51,51);"&gt;You will then be prompted for your organizational unit, organization, etc.&lt;/span&gt;&lt;br class="atl-forced-newline" /&gt;  &lt;br class="atl-forced-newline" /&gt; &lt;span style="color: rgb(51,51,51);"&gt;2. Generate the Certificate Signing Request (CSR)&lt;/span&gt;&lt;br class="atl-forced-newline" /&gt;  &lt;span style="color: rgb(51,51,51);"&gt;&lt;strong&gt;$JAVA_HOME/bin/keytool -certreq -alias tomcat -keystore /path/to/keystore.kdb -file servername.csr&lt;/strong&gt;&lt;/span&gt;&lt;br class="atl-forced-newline" /&gt;  &lt;br class="atl-forced-newline" /&gt;  &lt;span style="color: rgb(51,51,51);"&gt;3. Now go to&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&amp;nbsp;&lt;/span&gt;ipsCA&lt;span style="color: rgb(51,51,51);"&gt;&amp;nbsp;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;, select your certificate and fill in the form with your personal data, paste your certificate request in the CSR field and make sure that you include BEGIN NEW CERTIFICATE REQUEST and END NEW CERTIFICATE REQUEST in your copied text.&lt;/span&gt;&lt;br class="atl-forced-newline" /&gt;
&lt;br class="atl-forced-newline" /&gt;  &lt;span style="color: rgb(51,51,51);"&gt;4. Make a backup of the keystore.kdb key database. It would be useful for you if your server crashes.&lt;/span&gt;&lt;br class="atl-forced-newline" /&gt; &lt;/p&gt;&lt;/td&gt;
&lt;td&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;p&gt; &lt;span style="color: rgb(51,51,51);"&gt;&lt;strong&gt;Installing a Server Digital Certificate&lt;/strong&gt;&lt;/span&gt;&lt;br class="atl-forced-newline" /&gt; &lt;/p&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;p&gt; &lt;span style="color: rgb(51,51,51);"&gt;&lt;strong&gt;Upload a New SSL Certificate&lt;/strong&gt;&lt;/span&gt;&lt;br class="atl-forced-newline" /&gt;  &lt;span style="color: rgb(51,51,51);"&gt;After you receive your certificate,&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&amp;nbsp;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&lt;strong&gt;two other certificates will be necessary to setup your SSL Server, IPS SERVIDORES ROOT CERTIFICATE and the intermediate CA IPSCA CLASEA1&lt;/strong&gt;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;.&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&amp;nbsp;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&lt;strong&gt;It is essential that these certificates are also&amp;nbsp; installed on your webserver in order to establish correct SSL connections&lt;/strong&gt;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&amp;nbsp;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;with your customer's browsers. Should they be required, you may download these certificates individually or collectively as a bundled file below:&lt;/span&gt;&lt;br class="atl-forced-newline" /&gt;
IPSServidores.crt &lt;br class="atl-forced-newline" /&gt;
IPSCACLASEA1.crt &lt;br class="atl-forced-newline" /&gt;
IPS-IPSCABUNDLE.CRT &lt;br class="atl-forced-newline" /&gt;  &lt;span style="color: rgb(51,51,51);"&gt;You must first export the certificates in the following format:&lt;/span&gt;&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;&lt;span style="color: rgb(51,51,51);"&gt;Copy the&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&amp;nbsp;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&lt;em&gt;IPSCACLASEA1 Chained CA certificate&lt;/em&gt;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&amp;nbsp;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;into a text editor such as notepad and save as&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&amp;nbsp;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&lt;em&gt;chain.cer&lt;/em&gt;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&amp;nbsp;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;on a Windows machine with IE 5+.&lt;/span&gt;&lt;/li&gt;
	&lt;li&gt;&lt;span style="color: rgb(51,51,51);"&gt;Copy your&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&amp;nbsp;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&lt;em&gt;web server certificate&lt;/em&gt;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&amp;nbsp;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;into a text editor such as notepad and save as&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&lt;em&gt;yourdomain.cer&lt;/em&gt;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&amp;nbsp;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;on a Windows machine with IE 5+.&lt;/span&gt;&lt;/li&gt;
	&lt;li&gt;&lt;span style="color: rgb(51,51,51);"&gt;Copy the&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&amp;nbsp;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&lt;em&gt;IPSServidores root CA&lt;/em&gt;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&lt;em&gt;&amp;nbsp;&lt;/em&gt;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&lt;em&gt;certificate&lt;/em&gt;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&amp;nbsp;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;into a text editor and save as&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&amp;nbsp;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&lt;em&gt;root.cer&lt;/em&gt;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&lt;em&gt;&amp;nbsp;&lt;/em&gt;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;on a Windows machine with IE 5+.&lt;/span&gt;&lt;/li&gt;
	&lt;li&gt;&lt;span style="color: rgb(51,51,51);"&gt;Double-click the root.cer and select the Details tab, then Copy to File, then select the&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&amp;nbsp;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&lt;strong&gt;Base-64&lt;/strong&gt;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&amp;nbsp;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;option, give your copied certificate a file name of&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&amp;nbsp;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&lt;strong&gt;root_der.cer&lt;/strong&gt;&lt;/span&gt;&lt;/li&gt;
	&lt;li&gt;&lt;span style="color: rgb(51,51,51);"&gt;Double-click the chain.cer and select Install. Choose &amp;quot;Place all certificates in following store&amp;quot; and select Intermediate Certification Authorities. Complete the Wizard.&lt;/span&gt;&lt;/li&gt;
	&lt;li&gt;&lt;span style="color: rgb(51,51,51);"&gt;Double-click the chain.cer again and select the Details tab, then Copy to File, then select the&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&lt;strong&gt;Base-64&lt;/strong&gt;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&amp;nbsp;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;option, give your copied certificate a file name of&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&amp;nbsp;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&lt;strong&gt;chain_der.cer&lt;/strong&gt;&lt;/span&gt;&lt;/li&gt;
	&lt;li&gt;&lt;span style="color: rgb(51,51,51);"&gt;Double click the youdomain.cer and select the Details tab, then Copy to File, then select the&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&lt;strong&gt;PKCS#7 (p7b)&lt;/strong&gt;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&amp;nbsp;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;option, also select the&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&amp;nbsp;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&lt;strong&gt;Include all certificates in the certification path&lt;/strong&gt;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;, give your copied certificate a file name of&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&amp;nbsp;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&lt;strong&gt;yourdomain.p7b&lt;/strong&gt;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&lt;strong&gt;The following certificate installations must be executed in the stated order.&lt;/strong&gt;&lt;/span&gt;&lt;br class="atl-forced-newline" /&gt;  &lt;span style="color: rgb(51,51,51);"&gt;1. Import the&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&amp;nbsp;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&lt;strong&gt;root_der.cer&lt;/strong&gt;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&amp;nbsp;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;and&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&amp;nbsp;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&lt;strong&gt;chain_der.cer&lt;/strong&gt;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&amp;nbsp;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;files using:&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&lt;strong&gt;$ keytool -import -trustcacerts -keystore my.kdb -alias root - file root_der.cer&lt;/strong&gt;&lt;/span&gt;&lt;br class="atl-forced-newline" /&gt;  &lt;span style="color: rgb(51,51,51);"&gt;&lt;strong&gt;$ keytool -import -trustcacerts -keystore my.kdb -alias chain - file chain_der.cer&lt;/strong&gt;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;{*}&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;With my.kdb being your keystore.&lt;/span&gt;&lt;br class="atl-forced-newline" /&gt;  &lt;span style="color: rgb(51,51,51);"&gt;2. Import the&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&amp;nbsp;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&lt;strong&gt;yourdomain.p7b file&lt;/strong&gt;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&amp;nbsp;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;using:&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;{*}&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&lt;strong&gt;keytool -import -trustcacerts -keystore my.kdb -alias tomcat -file yourdomain.p7b&lt;/strong&gt;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;{*}&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;With my.kdb being your keystore.&lt;/span&gt;&lt;br class="atl-forced-newline" /&gt;  &lt;span style="color: rgb(51,51,51);"&gt;&amp;nbsp;&lt;/span&gt;&lt;br class="atl-forced-newline" /&gt;  &lt;span style="color: rgb(51,51,51);"&gt;{*}Update server.xml configuration&lt;/span&gt; &lt;span style="color: rgb(51,51,51);"&gt;file:\* (file:*)&lt;/span&gt;&lt;br class="atl-forced-newline" /&gt;  &lt;span style="color: rgb(51,51,51);"&gt;1. Open &amp;quot;$JAKARTA_HOME/conf/server.xml&amp;quot; in a text editor.&lt;/span&gt;&lt;br class="atl-forced-newline" /&gt;  &lt;span style="color: rgb(51,51,51);"&gt;2. Find the following section:&lt;/span&gt;&lt;br class="atl-forced-newline" /&gt;  &lt;span style="color: rgb(51,51,51);"&gt;&amp;lt;Connector&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&amp;nbsp;&lt;/span&gt;&lt;br class="atl-forced-newline" /&gt;  &lt;span style="color: rgb(51,51,51);"&gt;...&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&amp;nbsp;&lt;/span&gt;&lt;br class="atl-forced-newline" /&gt;  &lt;span style="color: rgb(51,51,51);"&gt;scheme=&amp;quot;https&amp;quot;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&amp;nbsp;&lt;/span&gt;&lt;br class="atl-forced-newline" /&gt;  &lt;span style="color: rgb(51,51,51);"&gt;secure=&amp;quot;true&amp;quot;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&amp;nbsp;&lt;/span&gt;&lt;br class="atl-forced-newline" /&gt;  &lt;span style="color: rgb(51,51,51);"&gt;keystoreFile=&amp;quot;/pathto/my.kdb&amp;quot;&lt;/span&gt;&lt;span style="color: rgb(51,51,51);"&gt;&amp;nbsp;&lt;/span&gt;&lt;br class="atl-forced-newline" /&gt;  &lt;span style="color: rgb(51,51,51);"&gt;keystorePass=&amp;quot;mypassword&amp;quot;&lt;/span&gt;&lt;br class="atl-forced-newline" /&gt;  &lt;span style="color: rgb(51,51,51);"&gt;3. If you want Tomcat to use the default SSL port, change all instances of the port number 8443 to 443.&lt;/span&gt;&lt;br class="atl-forced-newline" /&gt;  &lt;span style="color: rgb(51,51,51);"&gt;4. Add the keystoreFile and keystorePass directives to correspond with the keystore file and password that you are using.&lt;/span&gt;&lt;br class="atl-forced-newline" /&gt;  &lt;span style="color: rgb(51,51,51);"&gt;5. Start or restart Tomcat using the appropriate startup script (startup.sh for unix/linux or startup.bat for windows)&lt;/span&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;/td&gt;
&lt;td&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;&lt;/table&gt;
</property>
    

<property name="body">&lt;ac:structured-macro ac:macro-id="2f4b7cb2-4371-4c10-b189-20a22abd65c7" ac:name="info" ac:schema-version="1"&gt;&lt;ac:parameter ac:name="title"&gt;Description&lt;/ac:parameter&gt;&lt;ac:rich-text-body&gt;
&lt;p&gt;These instructions explain how to access our VPN using Linux without the Cisco vpn client.&lt;/p&gt;&lt;/ac:rich-text-body&gt;&lt;/ac:structured-macro&gt;

&lt;h2&gt;Setup&lt;/h2&gt;
&lt;ol&gt;
	&lt;li&gt;Install vpnc 
&lt;ac:structured-macro ac:macro-id="1dbc5e27-da88-46d9-b576-7bcee0049067" ac:name="code" ac:schema-version="1"&gt;&lt;ac:parameter ac:name="title"&gt;Ubuntu&lt;/ac:parameter&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[sudo apt-get install vpnc]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;/li&gt;
	&lt;li&gt;Place this file in /etc/vpnc/ &lt;ac:link&gt;&lt;ri:attachment ri:filename="suu.conf" /&gt;&lt;/ac:link&gt;&lt;/li&gt;
&lt;/ol&gt;


&lt;h2&gt;Running&lt;/h2&gt;
&lt;ol&gt;
	&lt;li&gt;&lt;ac:structured-macro ac:macro-id="471b1473-f3f1-4e49-b993-9731f884d76a" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[sudo vpnc suu]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;
 or 
&lt;ac:structured-macro ac:macro-id="afbe8a8e-91c6-4576-9678-02361a15dadb" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[sudo vpnc suu --no-detach]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;/li&gt;
&lt;/ol&gt;
</property>
    

<property name="body">h1. The latest client for Windows and Linux can be found on the isengard FTP server in the Tivoli\Linux or Tivoli\Windoze directory

h2. Example contents of dsm.opt file
{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Example contents of dsm.sys file
{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMmethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu

nodename &lt;servernodename_goeshere&gt; ex. ASPEN
passwordaccess generate
MANAGEDSERVICES	schedule webclient

exclude     /.../core
exclude     /.../tmp/.../*
exclude.dir /proc
exclude.dir /proc/
exclude.dir /dev
exclude.dir /dev/
exclude.dir	/mnt
exclude.dir	/mnt/
exclude.dir /usr/share/man
exclude dsmsched.log
{code}

h2. Configuring Automatic Startup
h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:
{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}
h4. Next, execute the following commands:
{code}
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}
h4. Finally, you must start the daemon manually and enter the password; this is only required once- it will remember it going forward
At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmcad
#dsmc
{code}
Once you run dsmc, it will prompt for a username and password.  Once you have entered them, you should be at a tsm prompt.  Enter the following:
{code}
backup
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.
{code}
Tivoli Upgrade Fix:

Upgrading Tivoli frequently breaks itself; this is the process to fix it after the fact.

1- Install the latest RPMS

2- Make soft links in the /usr/lib directory to all the .so files in /opt/tivoli/tsm/client/api/bin folder
cd /usr/lib
ln -s /opt/tivoli/tsm/client/api/bin/libct_cu.so libct_cu.so
ln -s /opt/tivoli/tsm/client/api/bin/libdmapi.so libdmapi.so
ln -s /opt/tivoli/tsm/client/api/bin/libgpfs.so libgpfs.so
ln -s /opt/tivoli/tsm/client/api/bin/libha_gs_r.so libha_gs_r.so
ln -s /opt/tivoli/tsm/client/api/bin/libxerces-c1_6_0.so libxerces-c1_6_0.so
ln -s /opt/tivoli/tsm/client/api/bin/libxmlutil-5.4.1.0.so libxmlutil-5.4.1.0.so


3- Make a soft link in the /opt/tivoli/tsm/client/ba/bin folder to /opt/tivoli/tsm/client/lang/en_US
ln -s /opt/tivoli/tsm/client/lang/en_US/ en_US

4- Stop and Start the process.
{code}</property>
    

<property name="body">h1. The latest client for Windows and Linux can be found on the isengard FTP server in the Tivoli\Linux or Tivoli\Windoze directory

h2. Example contents of dsm.opt file
{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Example contents of dsm.sys file
{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMmethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu

nodename &lt;servernodename_goeshere&gt; ex. ASPEN
passwordaccess generate
MANAGEDSERVICES	schedule webclient

exclude     /.../core
exclude     /.../tmp/.../*
exclude.dir /proc
exclude.dir /proc/
exclude.dir /dev
exclude.dir /dev/
exclude.dir	/mnt
exclude.dir	/mnt/
exclude.dir /usr/share/man
exclude dsmsched.log
{code}

h2. Configuring Automatic Startup
h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:
{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}
h4. Next, execute the following commands:
{code}
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}
h4. Finally, you must start the daemon manually and enter the password; this is only required once- it will remember it going forward
At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc i
#/etc/init.d/suu_tivoli start
{code}
Once you run dsmc, it will prompt for a username and password.  Once you have entered them, you should be at a tsm prompt.  Enter the following:
{code}
backup
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.
{code}
Tivoli Upgrade Fix:

Upgrading Tivoli frequently breaks itself; this is the process to fix it after the fact.

1- Install the latest RPMS

2- Make soft links in the /usr/lib directory to all the .so files in /opt/tivoli/tsm/client/api/bin folder
cd /usr/lib
ln -s /opt/tivoli/tsm/client/api/bin/libct_cu.so libct_cu.so
ln -s /opt/tivoli/tsm/client/api/bin/libdmapi.so libdmapi.so
ln -s /opt/tivoli/tsm/client/api/bin/libgpfs.so libgpfs.so
ln -s /opt/tivoli/tsm/client/api/bin/libha_gs_r.so libha_gs_r.so
ln -s /opt/tivoli/tsm/client/api/bin/libxerces-c1_6_0.so libxerces-c1_6_0.so
ln -s /opt/tivoli/tsm/client/api/bin/libxmlutil-5.4.1.0.so libxmlutil-5.4.1.0.so


3- Make a soft link in the /opt/tivoli/tsm/client/ba/bin folder to /opt/tivoli/tsm/client/lang/en_US
ln -s /opt/tivoli/tsm/client/lang/en_US/ en_US

4- Stop and Start the process.
{code}</property>
    

<property name="body">{code}
The key to creating self-signing certificates in Tomcat is to remember the key files/components involved:
&lt;yourkeystore&gt; and cacerts, and an existing Java HOME variable.


&lt;yourkeystore&gt; will be whatever you decide to call it when creating the self-signed certificate.  For example, the following
command creates a keystore called mykeystore with an alias of tomcat and a validity of 10 years in the C:\ssl directory:

%JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA -keystore C:\ssl\mykeystore -validity 3650
remember first and last name must be the host+domain, i.e. tntrans.suu.edu

Export it:
%JAVA_HOME%\bin\keytool -export -alias tomcat -file exported.cert -keystore C:\ssl\mykeystore

Once created, then you must import it into your existing CACERTS file for it to be 'trusted':

%JAVA_HOME%\bin\keytool -import -alias tomcat -trustcacerts -file D:\SSL\exported.cert -keystore %JAVA_HOME%\jre\lib\security\cacerts (this pass will be changeit)
{code}</property>
    

<property name="body">{info:title=Description}
These instructions explain how to access our VPN using Linux without the Cisco vpn client.
{info}

h2. Setup
# Install vpnc {code:title=Ubuntu}sudo apt-get install vpnc{code}
# Place this file in /etc/vpnc/ [^suu.conf]

h2. Running
# {{sudo vpnc suu}}</property>
    

<property name="body">{info:title=Description}
These instructions explain how to access our VPN using Linux without the Cisco vpn client.
{info}

h2. Setup
# Install vpnc {code:title=Ubuntu}sudo apt-get install vpnc{code}
# Place this file in /etc/vpnc/ [^suu.conf]

h2. Running
# {{sudo vpnc suu}} or {{sudo vpnc suu --no-detach}}</property>
    

<property name="body">&lt;ac:structured-macro ac:macro-id="0f555421-bf63-406c-ad16-24ae885b4d25" ac:name="info" ac:schema-version="1"&gt;&lt;ac:parameter ac:name="title"&gt;Description&lt;/ac:parameter&gt;&lt;ac:rich-text-body&gt;
&lt;p&gt;Say you have a file with email addresses in it along with other junk and you just want to pull out the email addresses into a file with one email address per line... well this is how you do it.&lt;/p&gt;&lt;/ac:rich-text-body&gt;&lt;/ac:structured-macro&gt;

&lt;ac:structured-macro ac:macro-id="dd1ce808-c39e-454e-b284-1fc02d30105f" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
cat list.txt | grep -o "[[:alnum:][:graph:]] *@[[:alnum:][:graph:]] *" &gt; newfile.txt
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;

&lt;p&gt;Where list.txt contains the emails along with other stuff and newfile.txt is the file with one email address per line.&lt;/p&gt;</property>
    

<property name="body">Linux space home page.</property>
    

<property name="body">Linux space home page.

{livesearch:id=1|spaceKey=linux}</property>
    

<property name="body">&lt;ac:structured-macro ac:macro-id="f255400c-9f2d-4828-8d0c-dbc73880aaf9" ac:name="info" ac:schema-version="1"&gt;&lt;ac:parameter ac:name="title"&gt;Description&lt;/ac:parameter&gt;&lt;ac:rich-text-body&gt;&lt;p&gt;PostgreSQL is an open source database. This document is a collection of notes for postgresql administrators.&lt;/p&gt;&lt;/ac:rich-text-body&gt;&lt;/ac:structured-macro&gt;&lt;h3&gt;Enabling remote connections to a postgresql database&lt;/h3&gt;&lt;p&gt;$POSTGRES_HOME will be something like &lt;code&gt;/etc/postgresql/8.3/main&lt;/code&gt;&lt;/p&gt;&lt;ac:structured-macro ac:macro-id="5dd4de3d-e03e-4350-94c7-6ddf1351a7f8" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[cd $POSTGRES_HOME
sudo vim postgresql.conf
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;p&gt;Find the line&lt;/p&gt;&lt;ac:structured-macro ac:macro-id="50b62112-30f4-4285-916f-ceab2333ddb3" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[#listen_address = 'localhost']] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;p&gt;and change it to&lt;/p&gt;&lt;ac:structured-macro ac:macro-id="c8313202-df34-48ae-a34e-79955a943e9b" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[listen_address = '*']] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;h1&gt;Theater Manager Database Upgrade Procedure&lt;/h1&gt;&lt;p&gt;On April 19, 2016, we were asked to upgrade the Theatre Manager Postgresql instance from 9.3 (the latest in the Ubuntu repos) to 9.5. &amp;nbsp;Here are the steps we took: (from&amp;nbsp;&lt;a href="http://no0p.github.io/postgresql/2014/03/29/upgrading-pg-ubuntu.html"&gt;http://no0p.github.io/postgresql/2014/03/29/upgrading-pg-ubuntu.html&lt;/a&gt;)&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p style="text-align: justify;"&gt;For more core concepts take a look at&amp;nbsp;&lt;a href="http://www.postgresql.org/docs/9.3/static/pgupgrade.html"&gt;the official documentation for pg_upgrade&lt;/a&gt;&amp;nbsp;tool.&lt;/p&gt;&lt;h2 style="text-align: justify;"&gt;Installing 9.5 alongside 9.3&lt;/h2&gt;&lt;p style="text-align: justify;"&gt;First we install 9.5 from the&amp;nbsp;&lt;a href="https://wiki.postgresql.org/wiki/Apt"&gt;postgres apt repos&lt;/a&gt;.&lt;/p&gt;&lt;pre&gt;&lt;code&gt;echo &amp;quot;deb http://apt.postgresql.org/pub/repos/apt/ precise-pgdg main&amp;quot; &amp;gt;
          /etc/apt/sources.list.d/pgdg.list
wget --quiet -O - https://www.postgresql.org/media/keys/ACCC4CF8.asc 
          | sudo apt-key add -
sudo apt-get update
sudo apt-get upgrade
sudo apt-get install postgresql-9.5 postgresql-contrib-9.5&lt;/code&gt;&lt;/pre&gt;&lt;p style="text-align: justify;"&gt;We note that the debian packages will start the 9.5 server and configure it to run on a port other than the port 9.3 is running on, likely 5433.&lt;/p&gt;&lt;p style="text-align: justify;"&gt;At this point, install any shared libraries which your 9.3 database has installed and are required for&amp;nbsp;&lt;code&gt;CREATE EXTENSION&lt;/code&gt;&amp;nbsp;commands to complete successfully. For example, if your 9.3 system uses postGIS, install postGIS packages for the 9.5 system. Identifying all extensions can be a laborious process since the pg_extension catalog table is scoped to the current database connection. Nonetheless it is absolutely necessary since the upgrade will fail without properly installed libraries.&lt;/p&gt;&lt;h2 style="text-align: justify;"&gt;Ensuring permissions&lt;/h2&gt;&lt;p style="text-align: justify;"&gt;To execute pg_upgrade the&amp;nbsp;&lt;strong&gt;postgres&lt;/strong&gt;&amp;nbsp;user will need to be able to connect to both databases. The databases will not be running on their normal ports for the upgrade, so it is somewhat safer to make less secure updates to pg_hba.conf. An entry like the following rule is pretty reasonable:&lt;/p&gt;&lt;pre&gt;&lt;code&gt;local   all             postgres                                peer&lt;/code&gt;&lt;/pre&gt;&lt;p style="text-align: justify;"&gt;Depending on your tolerance for farkling with pg_hba.conf you could also change all entries to trust.&lt;/p&gt;&lt;h2 style="text-align: justify;"&gt;Shutdown&lt;/h2&gt;&lt;p style="text-align: justify;"&gt;Neither database should be online during the upgrade process, as that could lead to an inconsistent copy.&lt;/p&gt;&lt;pre&gt;&lt;code&gt;sudo service postgresql stop 9.5
sudo service postgresql stop 9.3&lt;/code&gt;&lt;/pre&gt;&lt;p style="text-align: justify;"&gt;Great service is down.&lt;/p&gt;&lt;h2 style="text-align: justify;"&gt;Executing the upgrade, quickly&lt;/h2&gt;&lt;p style="text-align: justify;"&gt;When executed pg_upgrade starts both servers on an alternative port, runs some sanity checks, and performs the necessary conversion and copy routines. It&amp;rsquo;s simple to run:&lt;/p&gt;&lt;pre&gt;&lt;code&gt;sudo su postgres
/usr/lib/postgresql/9.5/bin/pg_upgrade -b /usr/lib/postgresql/9.3/bin/ 
          -B /usr/lib/postgresql/9.5/bin/ 
          -d /var/lib/postgresql/9.3/main 
          -D /var/lib/postgresql/9.5/main 
          -o ' -c config_file=/etc/postgresql/9.3/main/postgresql.conf'
          -O ' -c config_file=/etc/postgresql/9.5/main/postgresql.conf'&lt;/code&gt;&lt;/pre&gt;&lt;p style="text-align: justify;"&gt;Note that the command references the full path of the pg_upgrade binary. It&amp;rsquo;s important to use the binary for the target version.&lt;/p&gt;&lt;p style="text-align: justify;"&gt;If this command prints an error message see the section below titled Don&amp;rsquo;t Panic.&lt;/p&gt;&lt;h2 style="text-align: justify;"&gt;Starting the new server&lt;/h2&gt;&lt;p style="text-align: justify;"&gt;Now update the configuration in&amp;nbsp;&lt;code&gt;/etc/postgresql/9.5/main/postgresql.conf&lt;/code&gt;. Don&amp;rsquo;t copy the old file as it will contain old data and config directory directives. This is a great opportunity to review your GUCs.&lt;/p&gt;&lt;p style="text-align: justify;"&gt;Key updates are the&amp;nbsp;&lt;code&gt;listen_address&lt;/code&gt;&amp;nbsp;and&amp;nbsp;&lt;code&gt;port&lt;/code&gt;&amp;nbsp;directives. Then start the server carefully remembering the version suffix.&lt;/p&gt;&lt;pre&gt;&lt;code&gt; sudo service postgresql start 9.5&lt;/code&gt;&lt;/pre&gt;&lt;p style="text-align: justify;"&gt;You should now be able to restart all services which rely on the database and verify everything is working as expected.&lt;/p&gt;&lt;h2 style="text-align: justify;"&gt;Cleaning up&lt;/h2&gt;&lt;p style="text-align: justify;"&gt;Once satisified simply remove the 9.3 installation.&lt;/p&gt;&lt;pre&gt;&lt;code&gt; sudo apt-get remove postgresql-9.3&lt;/code&gt;&lt;/pre&gt;&lt;p style="text-align: justify;"&gt;You may choose to purge the package as well eventually.&lt;/p&gt;&lt;h2 style="text-align: justify;"&gt;Don&amp;rsquo;t panic&lt;/h2&gt;&lt;p style="text-align: justify;"&gt;Depending on your configuration, there is a chance that the pg_upgrade command will fail (safely). If this happens you have the option to just restart the old server and take a break.&lt;/p&gt;&lt;pre&gt;&lt;code&gt;sudo service postgresql start 9.3&lt;/code&gt;&lt;/pre&gt;&lt;p style="text-align: justify;"&gt;And take a moment to re-evaluate.&lt;/p&gt;&lt;p style="text-align: justify;"&gt;If you forgot about a 1TB tablespace on a rotating drive, it is okay to send an interrupt to pg_upgrade as long as you wipe the target database to a fresh install state.&lt;/p&gt;&lt;h2 style="text-align: justify;"&gt;Final Remarks&lt;/h2&gt;&lt;p style="text-align: justify;"&gt;This post covers a very basic upgrade process which allows for a downtime maintenance window. Its focus is on ease of safely completing the upgrade rather than minimizing downtime. There are pg_upgrade options you should be aware of such as direct linking the data files, which can save the time required to copy a potentially large database. Of course this is slightly more dangerous as it limits opportunities for backing out.&lt;/p&gt;&lt;p style="text-align: justify;"&gt;Good luck!&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;</property>
    

<property name="body">CUPS Doc
To install cups and hplip on a new server, here is the procedure:

CUPS:
1- ensure you have the following packages installed:
gcc, libjpeg, libjpeg-devel, libpng, libpng-devel, libtiff, libtiff-devel, zlib, zlib-devel,dbus-devel,php-devel,pyqt,pyqt-devel,xsane

2- Download the latest stable source from www.cups.org (1.3.6 as of this writing)

3- Compile the source as follows:
{code}rpmbuild -ta cups-version-source.tar.gz{code}

This will produce several compiled rpms in the /usr/src/redhat/RPMS/i386 directory.
The only ones you want are cups, cups-libs, cups-debuginfo, cups-devel,cups-lpd,cups-php
Do an rpm -Uvh on all these packages.

HPLIP:
{code}#tar -zxvf hplip-****.gz
#cd hplip-****
#(as banjobs, not ROOT) ./configure --enable-network-build --disable-pp-build --disable-fax-build --disable-gui-build --disable-scan-build --enable-doc-build --enable-foomatic-ppd-install --disable-foomatic-drv-install --with-hpppddir=/usr/share/cups/model/HP --disable-hpijs-only-build --prefix=/usr
#(as banjobs, not ROOT) make
#(as ROOT) make install
#/etc/init.d/hplip restart 
{code}

The following command creates a print queue called tranb on Solaris
lpadmin -p tranb -v/dev/null -m netstandard -o dest=134.250.51.248:3002 -T PS -I postscript -o protocol=tcp


--landscape using LPR

lpr  -o landscape -o cpi=15 -o lpi=12 -o cpi=16 -Pormond SHRTRTC_876.lis

Cups Options:

Jobs can also have options associated with them such as media size, number of copies, and priority.
CUPS supports collections of printers known as classes. Jobs sent to a class are forwarded to the first available printer in the class.
Filters allow a user or application to print many types of files without extra effort. Print jobs sent to a CUPS server are filtered before sending them to a printer.
 Some filters convert job files to different formats that the printer can understand. Others perform page selection and ordering tasks.

CUPS provides filters for printing many types of image files, HP-GL/2 files, PDF files, and text files.
 CUPS also supplies PostScript and image file Raster Image Processor ("RIP") filters that convert PostScript or image files into bitmaps that can be sent to a raster printer.
 
 
 CUPS also provides implicit classes, which are collections of printers and/or classes with the same name. This allows you to setup multiple servers pointing to the same physical network printer, 
 for example, so that you aren't relying on a single system for printing.  Because this also works with printer classes, you can setup multiple servers and printers
  and never worry about a single point of failure unless all of the printers and servers go down!
  
  General Options

The following options apply when printing all types of files.
Selecting the Media Size, Type, and Source

The -o media=xyz option sets the media size, type, and/or source:

      lp -o media=Letter filename ENTER
      lp -o media=Letter,MultiPurpose filename ENTER
      lpr -o media=Letter,Transparency filename ENTER
      lpr -o media=Letter,MultiPurpose,Transparency filename ENTER

The available media sizes, types, and sources depend on the printer, but most support the following options (case is not significant):

    * Letter - US Letter (8.5x11 inches, or 216x279mm)
    * Legal - US Legal (8.5x14 inches, or 216x356mm)
    * A4 - ISO A4 (8.27x11.69 inches, or 210x297mm)
    * COM10 - US #10 Envelope (9.5x4.125 inches, or 241x105mm)
    * DL - ISO DL Envelope (8.66x4.33 inches, or 220x110mm)
    * Transparency - Transparency media type or source
    * Upper - Upper paper tray
    * Lower - Lower paper tray
    * MultiPurpose - Multi-purpose paper tray
    * LargeCapacity - Large capacity paper tray

The actual options supported are defined in the printer's PPD file in the PageSize, InputSlot, and MediaType options.
Setting the Orientation

The -o landscape option will rotate the page 90 degrees to print in landscape orientation:

      lp -o landscape filename ENTER
      lpr -o landscape filename ENTER

Printing On Both Sides of the Paper

The -o sides=two-sided-short-edge and -o sides=two-sided-long-edge options will enable duplexing on the printer, if the printer supports it. The -o sides=two-sided-short-edge option is suitable for landscape pages, while the -o sides=two-sided-long-edge option is suitable for portrait pages:

      lp -o sides=two-sided-short-edge filename ENTER
      lp -o sides=two-sided-long-edge filename ENTER
      lpr -o sides=two-sided-long-edge filename ENTER

The default is to print single-sided:

      lp -o sides=one-sided filename ENTER
      lpr -o sides=one-sided filename ENTER

Banner Options

The following options apply when printing all types of files.
Selecting the Banner Page(s)

The -o jobsheets=start,end option sets the banner page(s) to use for a job:

      lp -o job-sheets=none filename ENTER
      lp -o job-sheets=standard filename ENTER
      lpr -o job-sheets=classified,classified filename ENTER

If only one banner file is specified, it will be printed before the files in the job. If a second banner file is specified, it is printed after the files in the job.

The available banner pages depend on the local system configuration; CUPS includes the following banner files:

    * none - Do not produce a banner page.
    * classified - A banner page with a "classified" label at the top and bottom.
    * confidential - A banner page with a "confidential" label at the top and bottom.
    * secret - A banner page with a "secret" label at the top and bottom.
    * standard - A banner page with no label at the top and bottom.
    * topsecret - A banner page with a "top secret" label at the top and bottom.
    * unclassified - A banner page with an "unclassified" label at the top and bottom.

Document Options

The following options apply when printing all types of files.
Selecting a Range of Pages

The -o page-ranges=pages option selects a range of pages for printing:

      lp -o page-ranges=1 filename ENTER
      lp -o page-ranges=1-4 filename ENTER
      lp -o page-ranges=1-4,7,9-12 filename ENTER
      lpr -o page-ranges=1-4,7,9-12 filename ENTER

As shown above, the pages value can be a single page, a range of pages, or a collection of page numbers and ranges separated by commas. The pages will always be printed in ascending order, regardless of the order of the pages in the page-ranges option.

The default is to print all pages.
Selecting Even or Odd Pages

Use the -o page-set=set option to select the even or odd pages:

      lp -o page-set=odd filename ENTER
      lp -o page-set=even filename ENTER
      lpr -o page-set=even filename ENTER

The default is to print all pages.
Setting the Output Order

The the -o outputorder=order option to set the output order of all pages:

      lp -o outputorder=normal filename ENTER
      lp -o outputorder=reverse filename ENTER
      lpr -o outputorder=reverse filename ENTER

N-Up Printing

The -o number-up=value option selects N-Up printing. N-Up printing places multiple document pages on a single printed page. CUPS supports 1, 2, 4, 6, 9, and 16-Up formats; the default format is 1-Up:

      lp -o number-up=1 filename ENTER
      lp -o number-up=2 filename ENTER
      lp -o number-up=4 filename ENTER
      lpr -o number-up=16 filename ENTER

The -o page-border=value option chooses the border to draw around each page:

    * -o page-border=double; draw two hairline borders around each page
    * -o page-border=double-thick; draw two 1pt borders around each page
    * -o page-border=none; do not draw a border (default)
    * -o page-border=single; draw one hairline border around each page
    * -o page-border=single-thick; draw one 1pt border around each page

The -o number-up-layout=value option chooses the layout of the pages on each output page:

    * -o number-up-layout=btlr; Bottom to top, left to right
    * -o number-up-layout=btrl; Bottom to top, right to left
    * -o number-up-layout=lrbt; Left to right, bottom to top
    * -o number-up-layout=lrtb; Left to right, top to bottom (default)
    * -o number-up-layout=rlbt; Right to left, bottom to top
    * -o number-up-layout=rltb; Right to left, top to bottom
    * -o number-up-layout=tblr; Top to bottom, left to right
    * -o number-up-layout=tbrl; Top to bottom, right to left

Mirroring Prints

You can mirror a print using the -o mirror option:

      lp -o mirror filename ENTER
      lpr -o mirror filename ENTER

This is useful for printing mirrored pages on transfer paper, for T shirts, mugs, etc.
Setting the Brightness

You can control the overall brightness of the printed output using the -o brightness=percent option:

      lp -o brightness=120 filename ENTER
      lpr -o brightness=120 filename ENTER

Values greater than 100 will lighten the print, while values less than 100 will darken it.
Setting the Gamma Correction

You can control the overall gamma correction of the printed output using the -o gamma=value option:

      lp -o gamma=1700 filename ENTER
      lpr -o gamma=1700 filename ENTER

Values greater than 1000 will lighten the print, while values less than 1000 will darken it. The default gamma is 1000.
Text Options

The following options apply when printing text files.
Setting the Number of Characters Per Inch

The -o cpi=value option sets the number of characters per inch:

      lp -o cpi=10 filename ENTER
      lp -o cpi=12 filename ENTER
      lpr -o cpi=17 filename ENTER

The default characters per inch is 10.
Setting the Number of Lines Per Inch

The -o lpi=value option sets the number of lines per inch:

      lp -o lpi=6 filename ENTER
      lpr -o lpi=8 filename ENTER

The default lines per inch is 6.
Setting the Number of Columns

The -o columns=value option sets the number of text columns:

      lp -o columns=2 filename ENTER
      lpr -o columns=3 filename ENTER

The default number of columns is 1.
Setting the Page Margins

Normally the page margins are set to the hard limits of the printer. Use the -o page-left=value, -o page-right=value , -o page-top=value, and -o page-bottom=value options to adjust the page margins:

      lp -o page-left=value filename ENTER
      lp -o page-right=value filename ENTER
      lp -o page-top=value filename ENTER
      lp -o page-bottom=value filename ENTER
      lpr -o page-bottom=value filename ENTER

The value argument is the margin in points; each point is 1/72 inch or 0.35mm.
Pretty Printing

The -o prettyprint option puts a header at the top of each page with the page number, job title (usually the filename), and the date. Also, C and C++ keywords are highlighted, and comment lines are italicized:

      lp -o prettyprint filename ENTER
      lpr -o prettyprint filename ENTER

Image Options

The following options apply when printing image files.
Positioning the Image

The -o position=name option specifies the position of the image on the page:

    * center - Center the image on the page (default)
    * top - Print the image centered at the top of the page
    * left - Print the image centered on the left of page
    * right - Print the image centered on the right of the page
    * top-left - Print the image at the top left corner of the page
    * top-right - Print the image at the top right corner of the page
    * bottom - Print the image centered at the bottom of the page
    * bottom-left - Print the image at the bottom left corner of the page
    * bottom-right - Print the image at the bottom right corner of the page

Scaling the Image

The -o scaling=percent, -o ppi=value, and -o natural-scaling=percent options change the size of a printed image:

      lp -o scaling=percent filename ENTER
      lp -o ppi=value filename ENTER
      lpr -o natural-scaling=percent filename ENTER

The scaling=percent value is a number from 1 to 800 specifying the size in relation to the page (not the image.) A scaling of 100 percent will fill the page as completely as the image aspect ratio allows. A scaling of 200 percent will print on up to 4 pages.

The ppi=value value is a number from 1 to 1200 specifying the resolution of the image in pixels per inch. An image that is 3000x2400 pixels will print 10x8 inches at 300 pixels per inch, for example. If the specified resolution makes the image larger than the page, multiple pages will be printed to satisfy the request.

The natural-scaling=percent value is a number from 1 to 800 specifying the size in relation to the natural image size. A scaling of 100 percent will print the image at its natural size, while a scaling of 50 percent will print the image at half its natural size. If the specified scaling makes the image larger than the page, multiple pages will be printed to satisfy the request.
Adjusting the Hue (Tint) of an Image

The -o hue=value option will adjust the hue of the printed image, much like the tint control on your television:

      lp -o hue=value filename ENTER
      lpr -o hue=value filename ENTER

The value argument is a number from -360 to 360 and represents the color hue rotation. The following table summarizes the change you'll see with different colors:
Original	hue=-45	hue=45
Red	Purple	Yellow-orange
Green	Yellow-green	Blue-green
Yellow	Orange	Green-yellow
Blue	Sky-blue	Purple
Magenta	Indigo	Crimson
Cyan	Blue-green	Light-navy-blue

The default hue adjustment is 0.
Adjusting the Saturation (Color) of an Image

The -o saturation=percent option adjusts the saturation of the colors in an image, much like the color knob on your television:

      lp -o saturation=percent filename ENTER
      lpr -o saturation=percent filename ENTER

The percent argument specifies the color saturation from 0 to 200. A color saturation of 0 produces a black-and-white print, while a value of 200 will make the colors extremely intense.

The default saturation is 100.
HP-GL/2 Options

The following options apply to HP-GL/2 files.
Printing in Black

The -o blackplot option specifies that all pens should plot in black:

      lp -o blackplot filename ENTER
      lpr -o blackplot filename ENTER

The default is to use the colors defined in the plot file or the standard pen colors defined in the HP-GL/2 reference manual from Hewlett Packard.
Fitting the Plot on the Page

The -o fitplot option specifies that the plot should be scaled to fit on the page:

      lp -o fitplot filename ENTER
      lpr -o fitplot filename ENTER

The default is to use the absolute distances specified in the plot file.
NOTE:

This feature depends upon an accurate plot size (PS) command in the HP-GL/2 file. If no plot size is given in the file than the HP-GL/2 filter assumes the plot is ANSI E size.

Setting the Default Pen Width

The -o penwidth=value option specifies the default pen width for HP-GL/2 files:

      lp -o penwidth=value filename ENTER
      lpr -o penwidth=value filename ENTER

The pen width value specifies the pen width in micrometers. The default value of 1000 produces lines that are 1 millimeter in width. Specifying a pen width of 0 produces lines that are exactly 1 pixel wide.
NOTE:

This option is ignored when the pen widths are set in the plot file.

Raw or Unfiltered Output

The -o raw option allows you to send files directly to a printer without filtering. This is sometimes required when printing from applications that provide their own "printer drivers" for your printer:

      lp -o raw filename ENTER
      lpr -o raw filename ENTER

The -l option can also be used with the lpr command to send files directly to a printer:

      lpr -l filename ENTER

4 - Saving Printer Options and Defaults

This chapter describes how to save printer options for your printer and set your own default printer.
Printer Options

Each printer supports a large number of options, which you learned about in Chapter 3, "Standard Printer Options". Rather than specifying these options each time you print a file, CUPS allows you to save them as "default" options for the printer.

The lpoptions(1) command saves the options for your printers. Like the lp and lpr commands, it accepts printer options using the -o argument:

      lpoptions -o prettyprint ENTER
      lpoptions -o media=A4 -o sides=two-sided-long-edge ENTER
      lpoptions -o media=Legal -o scaling=100 ENTER

Once saved, any lp or lpr command will use them when you print.
Note:

Running the lpoptions command as the root user (or any user with a UID of 0) will set the default options for all users. The root account does not have its own set of default options.

Setting Options for a Specific Printer

The previous example shows how to set the options for the default printer. The -p printer option specifies the options are for another printer:

      lpoptions -p laserjet -o prettyprint ENTER
      lpoptions -p laserjet -o media=A4 -o sides=two-sided-long-edge ENTER
      lpoptions -p deskjet -o media=Legal -o scaling=100 ENTER

Removing Options

The previous two examples shows how to set options for the default and a specific printer. Below, shows you how to remove the saved option using the -r argument:

      lpoptions -r prettyprint ENTER
      lpoptions -p laserjet -r prettyprint ENTER

Viewing the Current Defaults

The lpoptions command can also be used to show the current options by not specifying any new options on the command-line:

      lpoptions ENTER
      media=A4 sides=two-sided-long-edge
      lpoptions -p deskjet ENTER
      media=Legal scaling=100

Viewing Options for a Specific Printer

You can display the supported options using the lpoptions command with the -l option, as follows:

      lpoptions -p laserjet -l ENTER

Setting the Default Printer

The administrator normally will set a system-wide default printer that is normally used as the default printer by everyone. Use the -d printer option to set your own default printer:

      lpoptions -d deskjet ENTER

The printer can be local (deskjet) or remote ( deskjet@server).
Printer Instances

Besides setting options for each print queue, CUPS supports printer instances which allow you to define several different sets of options for each printer. You specify a printer instance using the slash (/) character:

      lpoptions -p laserjet/duplex -o sides=two-sided-long-edge ENTER
      lpoptions -p laserjet/legal -o media=Legal ENTER

The lp and lpr commands also understand this notation:

      lp -d laserjet/duplex filename ENTER
      lpr -P laserjet/legal filename ENTER

Removing Instances

Use the -x printer/instance option to remove a printer instance that you no longer need:

      lpoptions -x laserjet ENTER
      lpoptions -x laserjet/duplex ENTER
      lpoptions -x laserjet/legal ENTER

The -x option only removes the default options for that printer and instance; the original print queue will remain until deleted with the lpadmin(8) command by the administrator.


# Allow printing to printer MyLaserJet from 
#    itself and computers 192.10.2.5 and 192.10.2.6
&lt;Location /printers/MyLaserJet&gt;
...
Order deny,allow
Deny from all
Allow from 127.0.0.1
Allow from 192.10.2.5
Allow from 192.10.2.6
&lt;/Location&gt;

# Allow printing to printer MyLaserJet from 
#    itself and all computers on subnet 192.10.2.x
&lt;Location /printers/MyLaserJet&gt;
...
Order deny,allow
Deny from all
Allow from 127.0.0.1
Allow from 192.10.2.0/255.255.255.0
&lt;/Location&gt;</property>
    

<property name="body">CUPS Doc
To install cups and hplip on a new server, here is the procedure:

CUPS:
1\- ensure you have the following packages installed:
gcc, libjpeg, libjpeg-devel, libpng, libpng-devel, libtiff, libtiff-devel, zlib, zlib-devel,dbus-devel,php-devel,pyqt,pyqt-devel,xsane,net-snmp-devel


2\- Download the latest stable source from www.cups.org (1.3.6 as of this writing)

3\- Compile the source as follows:
{code}
rpmbuild -ta cups-version-source.tar.gz
{code}
This will produce several compiled rpms in the /usr/src/redhat/RPMS/i386 directory.
The only ones you want are cups, cups-libs, cups-debuginfo, cups-devel,cups-lpd,cups-php
Do an rpm \-Uvh on all these packages.

HPLIP:
{code}
#tar -zxvf hplip-****.gz
#cd hplip-****
#(as banjobs, not ROOT) ./configure --enable-network-build --disable-pp-build --disable-fax-build --disable-gui-build --disable-scan-build --enable-doc-build --enable-foomatic-ppd-install --disable-foomatic-drv-install --with-hpppddir=/usr/share/cups/model/HP --disable-hpijs-only-build --prefix=/usr
#(as banjobs, not ROOT) make
#(as ROOT) make install
#/etc/init.d/hplip restart
{code}
The following command creates a print queue called tranb on Solaris
lpadmin \-p tranb \-v/dev/null \-m netstandard \-o dest=134.250.51.248:3002 \-T PS \-I postscript \-o protocol=tcp

\--landscape using LPR

lpr  \-o landscape \-o cpi=15 \-o lpi=12 \-o cpi=16 \-Pormond SHRTRTC_876.lis

Cups Options:

Jobs can also have options associated with them such as media size, number of copies, and priority.
CUPS supports collections of printers known as classes. Jobs sent to a class are forwarded to the first available printer in the class.
Filters allow a user or application to print many types of files without extra effort. Print jobs sent to a CUPS server are filtered before sending them to a printer.
Some filters convert job files to different formats that the printer can understand. Others perform page selection and ordering tasks.

CUPS provides filters for printing many types of image files, HP-GL/2 files, PDF files, and text files.
CUPS also supplies PostScript and image file Raster Image Processor ("RIP") filters that convert PostScript or image files into bitmaps that can be sent to a raster printer.

CUPS also provides implicit classes, which are collections of printers and/or classes with the same name. This allows you to setup multiple servers pointing to the same physical network printer,
for example, so that you aren't relying on a single system for printing.  Because this also works with printer classes, you can setup multiple servers and printers
and never worry about a single point of failure unless all of the printers and servers go down\!

General Options

The following options apply when printing all types of files.
Selecting the Media Size, Type, and Source

The \-o media=xyz option sets the media size, type, and/or source:

lp \-o media=Letter filename ENTER
lp \-o media=Letter,MultiPurpose filename ENTER
lpr \-o media=Letter,Transparency filename ENTER
lpr \-o media=Letter,MultiPurpose,Transparency filename ENTER

The available media sizes, types, and sources depend on the printer, but most support the following options (case is not significant):
* Letter - US Letter (8.5x11 inches, or 216x279mm)
* Legal - US Legal (8.5x14 inches, or 216x356mm)
* A4 - ISO A4 (8.27x11.69 inches, or 210x297mm)
* COM10 - US #10 Envelope (9.5x4.125 inches, or 241x105mm)
* DL - ISO DL Envelope (8.66x4.33 inches, or 220x110mm)
* Transparency - Transparency media type or source
* Upper - Upper paper tray
* Lower - Lower paper tray
* MultiPurpose - Multi-purpose paper tray
* LargeCapacity - Large capacity paper tray

The actual options supported are defined in the printer's PPD file in the PageSize, InputSlot, and MediaType options.
Setting the Orientation

The \-o landscape option will rotate the page 90 degrees to print in landscape orientation:

lp \-o landscape filename ENTER
lpr \-o landscape filename ENTER

Printing On Both Sides of the Paper

The \-o sides=two-sided-short-edge and \-o sides=two-sided-long-edge options will enable duplexing on the printer, if the printer supports it. The \-o sides=two-sided-short-edge option is suitable for landscape pages, while the \-o sides=two-sided-long-edge option is suitable for portrait pages:

lp \-o sides=two-sided-short-edge filename ENTER
lp \-o sides=two-sided-long-edge filename ENTER
lpr \-o sides=two-sided-long-edge filename ENTER

The default is to print single-sided:

lp \-o sides=one-sided filename ENTER
lpr \-o sides=one-sided filename ENTER

Banner Options

The following options apply when printing all types of files.
Selecting the Banner Page(s)

The \-o jobsheets=start,end option sets the banner page(s) to use for a job:

lp \-o job-sheets=none filename ENTER
lp \-o job-sheets=standard filename ENTER
lpr \-o job-sheets=classified,classified filename ENTER

If only one banner file is specified, it will be printed before the files in the job. If a second banner file is specified, it is printed after the files in the job.

The available banner pages depend on the local system configuration; CUPS includes the following banner files:
* none - Do not produce a banner page.
* classified - A banner page with a "classified" label at the top and bottom.
* confidential - A banner page with a "confidential" label at the top and bottom.
* secret - A banner page with a "secret" label at the top and bottom.
* standard - A banner page with no label at the top and bottom.
* topsecret - A banner page with a "top secret" label at the top and bottom.
* unclassified - A banner page with an "unclassified" label at the top and bottom.

Document Options

The following options apply when printing all types of files.
Selecting a Range of Pages

The \-o page-ranges=pages option selects a range of pages for printing:

lp \-o page-ranges=1 filename ENTER
lp \-o page-ranges=1-4 filename ENTER
lp \-o page-ranges=1-4,7,9-12 filename ENTER
lpr \-o page-ranges=1-4,7,9-12 filename ENTER

As shown above, the pages value can be a single page, a range of pages, or a collection of page numbers and ranges separated by commas. The pages will always be printed in ascending order, regardless of the order of the pages in the page-ranges option.

The default is to print all pages.
Selecting Even or Odd Pages

Use the \-o page-set=set option to select the even or odd pages:

lp \-o page-set=odd filename ENTER
lp \-o page-set=even filename ENTER
lpr \-o page-set=even filename ENTER

The default is to print all pages.
Setting the Output Order

The the \-o outputorder=order option to set the output order of all pages:

lp \-o outputorder=normal filename ENTER
lp \-o outputorder=reverse filename ENTER
lpr \-o outputorder=reverse filename ENTER

N-Up Printing

The \-o number-up=value option selects N-Up printing. N-Up printing places multiple document pages on a single printed page. CUPS supports 1, 2, 4, 6, 9, and 16-Up formats; the default format is 1-Up:

lp \-o number-up=1 filename ENTER
lp \-o number-up=2 filename ENTER
lp \-o number-up=4 filename ENTER
lpr \-o number-up=16 filename ENTER

The \-o page-border=value option chooses the border to draw around each page:
* \-o page-border=double; draw two hairline borders around each page
* \-o page-border=double-thick; draw two 1pt borders around each page
* \-o page-border=none; do not draw a border (default)
* \-o page-border=single; draw one hairline border around each page
* \-o page-border=single-thick; draw one 1pt border around each page

The \-o number-up-layout=value option chooses the layout of the pages on each output page:
* \-o number-up-layout=btlr; Bottom to top, left to right
* \-o number-up-layout=btrl; Bottom to top, right to left
* \-o number-up-layout=lrbt; Left to right, bottom to top
* \-o number-up-layout=lrtb; Left to right, top to bottom (default)
* \-o number-up-layout=rlbt; Right to left, bottom to top
* \-o number-up-layout=rltb; Right to left, top to bottom
* \-o number-up-layout=tblr; Top to bottom, left to right
* \-o number-up-layout=tbrl; Top to bottom, right to left

Mirroring Prints

You can mirror a print using the \-o mirror option:

lp \-o mirror filename ENTER
lpr \-o mirror filename ENTER

This is useful for printing mirrored pages on transfer paper, for T shirts, mugs, etc.
Setting the Brightness

You can control the overall brightness of the printed output using the \-o brightness=percent option:

lp \-o brightness=120 filename ENTER
lpr \-o brightness=120 filename ENTER

Values greater than 100 will lighten the print, while values less than 100 will darken it.
Setting the Gamma Correction

You can control the overall gamma correction of the printed output using the \-o gamma=value option:

lp \-o gamma=1700 filename ENTER
lpr \-o gamma=1700 filename ENTER

Values greater than 1000 will lighten the print, while values less than 1000 will darken it. The default gamma is 1000.
Text Options

The following options apply when printing text files.
Setting the Number of Characters Per Inch

The \-o cpi=value option sets the number of characters per inch:

lp \-o cpi=10 filename ENTER
lp \-o cpi=12 filename ENTER
lpr \-o cpi=17 filename ENTER

The default characters per inch is 10.
Setting the Number of Lines Per Inch

The \-o lpi=value option sets the number of lines per inch:

lp \-o lpi=6 filename ENTER
lpr \-o lpi=8 filename ENTER

The default lines per inch is 6.
Setting the Number of Columns

The \-o columns=value option sets the number of text columns:

lp \-o columns=2 filename ENTER
lpr \-o columns=3 filename ENTER

The default number of columns is 1.
Setting the Page Margins

Normally the page margins are set to the hard limits of the printer. Use the \-o page-left=value, \-o page-right=value , \-o page-top=value, and \-o page-bottom=value options to adjust the page margins:

lp \-o page-left=value filename ENTER
lp \-o page-right=value filename ENTER
lp \-o page-top=value filename ENTER
lp \-o page-bottom=value filename ENTER
lpr \-o page-bottom=value filename ENTER

The value argument is the margin in points; each point is 1/72 inch or 0.35mm.
Pretty Printing

The \-o prettyprint option puts a header at the top of each page with the page number, job title (usually the filename), and the date. Also, C and C+\+ keywords are highlighted, and comment lines are italicized:

lp \-o prettyprint filename ENTER
lpr \-o prettyprint filename ENTER

Image Options

The following options apply when printing image files.
Positioning the Image

The \-o position=name option specifies the position of the image on the page:
* center - Center the image on the page (default)
* top - Print the image centered at the top of the page
* left - Print the image centered on the left of page
* right - Print the image centered on the right of the page
* top-left - Print the image at the top left corner of the page
* top-right - Print the image at the top right corner of the page
* bottom - Print the image centered at the bottom of the page
* bottom-left - Print the image at the bottom left corner of the page
* bottom-right - Print the image at the bottom right corner of the page

Scaling the Image

The \-o scaling=percent, \-o ppi=value, and \-o natural-scaling=percent options change the size of a printed image:

lp \-o scaling=percent filename ENTER
lp \-o ppi=value filename ENTER
lpr \-o natural-scaling=percent filename ENTER

The scaling=percent value is a number from 1 to 800 specifying the size in relation to the page (not the image.) A scaling of 100 percent will fill the page as completely as the image aspect ratio allows. A scaling of 200 percent will print on up to 4 pages.

The ppi=value value is a number from 1 to 1200 specifying the resolution of the image in pixels per inch. An image that is 3000x2400 pixels will print 10x8 inches at 300 pixels per inch, for example. If the specified resolution makes the image larger than the page, multiple pages will be printed to satisfy the request.

The natural-scaling=percent value is a number from 1 to 800 specifying the size in relation to the natural image size. A scaling of 100 percent will print the image at its natural size, while a scaling of 50 percent will print the image at half its natural size. If the specified scaling makes the image larger than the page, multiple pages will be printed to satisfy the request.
Adjusting the Hue (Tint) of an Image

The \-o hue=value option will adjust the hue of the printed image, much like the tint control on your television:

lp \-o hue=value filename ENTER
lpr \-o hue=value filename ENTER

The value argument is a number from \-360 to 360 and represents the color hue rotation. The following table summarizes the change you'll see with different colors:
Original	hue=-45	hue=45
Red	Purple	Yellow-orange
Green	Yellow-green	Blue-green
Yellow	Orange	Green-yellow
Blue	Sky-blue	Purple
Magenta	Indigo	Crimson
Cyan	Blue-green	Light-navy-blue

The default hue adjustment is 0.
Adjusting the Saturation (Color) of an Image

The \-o saturation=percent option adjusts the saturation of the colors in an image, much like the color knob on your television:

lp \-o saturation=percent filename ENTER
lpr \-o saturation=percent filename ENTER

The percent argument specifies the color saturation from 0 to 200. A color saturation of 0 produces a black-and-white print, while a value of 200 will make the colors extremely intense.

The default saturation is 100.
HP-GL/2 Options

The following options apply to HP-GL/2 files.
Printing in Black

The \-o blackplot option specifies that all pens should plot in black:

lp \-o blackplot filename ENTER
lpr \-o blackplot filename ENTER

The default is to use the colors defined in the plot file or the standard pen colors defined in the HP-GL/2 reference manual from Hewlett Packard.
Fitting the Plot on the Page

The \-o fitplot option specifies that the plot should be scaled to fit on the page:

lp \-o fitplot filename ENTER
lpr \-o fitplot filename ENTER

The default is to use the absolute distances specified in the plot file.
NOTE:

This feature depends upon an accurate plot size (PS) command in the HP-GL/2 file. If no plot size is given in the file than the HP-GL/2 filter assumes the plot is ANSI E size.

Setting the Default Pen Width

The \-o penwidth=value option specifies the default pen width for HP-GL/2 files:

lp \-o penwidth=value filename ENTER
lpr \-o penwidth=value filename ENTER

The pen width value specifies the pen width in micrometers. The default value of 1000 produces lines that are 1 millimeter in width. Specifying a pen width of 0 produces lines that are exactly 1 pixel wide.
NOTE:

This option is ignored when the pen widths are set in the plot file.

Raw or Unfiltered Output

The \-o raw option allows you to send files directly to a printer without filtering. This is sometimes required when printing from applications that provide their own "printer drivers" for your printer:

lp \-o raw filename ENTER
lpr \-o raw filename ENTER

The \-l option can also be used with the lpr command to send files directly to a printer:

lpr \-l filename ENTER

4 - Saving Printer Options and Defaults

This chapter describes how to save printer options for your printer and set your own default printer.
Printer Options

Each printer supports a large number of options, which you learned about in Chapter 3, "Standard Printer Options". Rather than specifying these options each time you print a file, CUPS allows you to save them as "default" options for the printer.

The lpoptions(1) command saves the options for your printers. Like the lp and lpr commands, it accepts printer options using the \-o argument:

lpoptions \-o prettyprint ENTER
lpoptions \-o media=A4 \-o sides=two-sided-long-edge ENTER
lpoptions \-o media=Legal \-o scaling=100 ENTER

Once saved, any lp or lpr command will use them when you print.
Note:

Running the lpoptions command as the root user (or any user with a UID of 0) will set the default options for all users. The root account does not have its own set of default options.

Setting Options for a Specific Printer

The previous example shows how to set the options for the default printer. The \-p printer option specifies the options are for another printer:

lpoptions \-p laserjet \-o prettyprint ENTER
lpoptions \-p laserjet \-o media=A4 \-o sides=two-sided-long-edge ENTER
lpoptions \-p deskjet \-o media=Legal \-o scaling=100 ENTER

Removing Options

The previous two examples shows how to set options for the default and a specific printer. Below, shows you how to remove the saved option using the \-r argument:

lpoptions \-r prettyprint ENTER
lpoptions \-p laserjet \-r prettyprint ENTER

Viewing the Current Defaults

The lpoptions command can also be used to show the current options by not specifying any new options on the command-line:

lpoptions ENTER
media=A4 sides=two-sided-long-edge
lpoptions \-p deskjet ENTER
media=Legal scaling=100

Viewing Options for a Specific Printer

You can display the supported options using the lpoptions command with the \-l option, as follows:

lpoptions \-p laserjet \-l ENTER

Setting the Default Printer

The administrator normally will set a system-wide default printer that is normally used as the default printer by everyone. Use the \-d printer option to set your own default printer:

lpoptions \-d deskjet ENTER

The printer can be local (deskjet) or remote ( deskjet@server).
Printer Instances

Besides setting options for each print queue, CUPS supports printer instances which allow you to define several different sets of options for each printer. You specify a printer instance using the slash (/) character:

lpoptions \-p laserjet/duplex \-o sides=two-sided-long-edge ENTER
lpoptions \-p laserjet/legal \-o media=Legal ENTER

The lp and lpr commands also understand this notation:

lp \-d laserjet/duplex filename ENTER
lpr \-P laserjet/legal filename ENTER

Removing Instances

Use the \-x printer/instance option to remove a printer instance that you no longer need:

lpoptions \-x laserjet ENTER
lpoptions \-x laserjet/duplex ENTER
lpoptions \-x laserjet/legal ENTER

The \-x option only removes the default options for that printer and instance; the original print queue will remain until deleted with the lpadmin(8) command by the administrator.
# Allow printing to printer MyLaserJet from
# itself and computers 192.10.2.5 and 192.10.2.6
&lt;Location /printers/MyLaserJet&gt;
...
Order deny,allow
Deny from all
Allow from 127.0.0.1
Allow from 192.10.2.5
Allow from 192.10.2.6
&lt;/Location&gt;

# Allow printing to printer MyLaserJet from
# itself and all computers on subnet 192.10.2.x
&lt;Location /printers/MyLaserJet&gt;
...
Order deny,allow
Deny from all
Allow from 127.0.0.1
Allow from 192.10.2.0/255.255.255.0
&lt;/Location&gt;</property>
    

<property name="body">CUPS Doc
To install cups and hplip on a new server, here is the procedure:

CUPS:
1\- ensure you have the following packages installed:
gcc, libjpeg, libjpeg-devel, libpng, libpng-devel, libtiff, libtiff-devel, zlib, zlib-devel,dbus-devel,php-devel,pyqt,pyqt-devel,xsane,net-snmp-devel

2\- Download the latest stable source from www.cups.org (1.3.6 as of this writing)

3\- Compile the source as follows:
{code}
rpmbuild -ta cups-version-source.tar.gz --without-dbus
{code}
This will produce several compiled rpms in the /usr/src/redhat/RPMS/i386 directory.
The only ones you want are cups, cups-libs, cups-debuginfo, cups-devel,cups-lpd,cups-php
Do an rpm \-Uvh on all these packages.

HPLIP:
{code}
#tar -zxvf hplip-****.gz
#cd hplip-****
#(as banjobs, not ROOT) ./configure --enable-network-build --disable-pp-build --disable-fax-build --disable-gui-build --disable-scan-build --enable-doc-build --enable-foomatic-ppd-install --disable-foomatic-drv-install --with-hpppddir=/usr/share/cups/model/HP --disable-hpijs-only-build --prefix=/usr
#(as banjobs, not ROOT) make
#(as ROOT) make install
#/etc/init.d/hplip restart
{code}
The following command creates a print queue called tranb on Solaris
lpadmin \-p tranb \-v/dev/null \-m netstandard \-o dest=134.250.51.248:3002 \-T PS \-I postscript \-o protocol=tcp

\--landscape using LPR

lpr  \-o landscape \-o cpi=15 \-o lpi=12 \-o cpi=16 \-Pormond SHRTRTC_876.lis

Cups Options:

Jobs can also have options associated with them such as media size, number of copies, and priority.
CUPS supports collections of printers known as classes. Jobs sent to a class are forwarded to the first available printer in the class.
Filters allow a user or application to print many types of files without extra effort. Print jobs sent to a CUPS server are filtered before sending them to a printer.
Some filters convert job files to different formats that the printer can understand. Others perform page selection and ordering tasks.

CUPS provides filters for printing many types of image files, HP-GL/2 files, PDF files, and text files.
CUPS also supplies PostScript and image file Raster Image Processor ("RIP") filters that convert PostScript or image files into bitmaps that can be sent to a raster printer.

CUPS also provides implicit classes, which are collections of printers and/or classes with the same name. This allows you to setup multiple servers pointing to the same physical network printer,
for example, so that you aren't relying on a single system for printing.  Because this also works with printer classes, you can setup multiple servers and printers
and never worry about a single point of failure unless all of the printers and servers go down\!

General Options

The following options apply when printing all types of files.
Selecting the Media Size, Type, and Source

The \-o media=xyz option sets the media size, type, and/or source:

lp \-o media=Letter filename ENTER
lp \-o media=Letter,MultiPurpose filename ENTER
lpr \-o media=Letter,Transparency filename ENTER
lpr \-o media=Letter,MultiPurpose,Transparency filename ENTER

The available media sizes, types, and sources depend on the printer, but most support the following options (case is not significant):
* Letter - US Letter (8.5x11 inches, or 216x279mm)
* Legal - US Legal (8.5x14 inches, or 216x356mm)
* A4 - ISO A4 (8.27x11.69 inches, or 210x297mm)
* COM10 - US #10 Envelope (9.5x4.125 inches, or 241x105mm)
* DL - ISO DL Envelope (8.66x4.33 inches, or 220x110mm)
* Transparency - Transparency media type or source
* Upper - Upper paper tray
* Lower - Lower paper tray
* MultiPurpose - Multi-purpose paper tray
* LargeCapacity - Large capacity paper tray

The actual options supported are defined in the printer's PPD file in the PageSize, InputSlot, and MediaType options.
Setting the Orientation

The \-o landscape option will rotate the page 90 degrees to print in landscape orientation:

lp \-o landscape filename ENTER
lpr \-o landscape filename ENTER

Printing On Both Sides of the Paper

The \-o sides=two-sided-short-edge and \-o sides=two-sided-long-edge options will enable duplexing on the printer, if the printer supports it. The \-o sides=two-sided-short-edge option is suitable for landscape pages, while the \-o sides=two-sided-long-edge option is suitable for portrait pages:

lp \-o sides=two-sided-short-edge filename ENTER
lp \-o sides=two-sided-long-edge filename ENTER
lpr \-o sides=two-sided-long-edge filename ENTER

The default is to print single-sided:

lp \-o sides=one-sided filename ENTER
lpr \-o sides=one-sided filename ENTER

Banner Options

The following options apply when printing all types of files.
Selecting the Banner Page(s)

The \-o jobsheets=start,end option sets the banner page(s) to use for a job:

lp \-o job-sheets=none filename ENTER
lp \-o job-sheets=standard filename ENTER
lpr \-o job-sheets=classified,classified filename ENTER

If only one banner file is specified, it will be printed before the files in the job. If a second banner file is specified, it is printed after the files in the job.

The available banner pages depend on the local system configuration; CUPS includes the following banner files:
* none - Do not produce a banner page.
* classified - A banner page with a "classified" label at the top and bottom.
* confidential - A banner page with a "confidential" label at the top and bottom.
* secret - A banner page with a "secret" label at the top and bottom.
* standard - A banner page with no label at the top and bottom.
* topsecret - A banner page with a "top secret" label at the top and bottom.
* unclassified - A banner page with an "unclassified" label at the top and bottom.

Document Options

The following options apply when printing all types of files.
Selecting a Range of Pages

The \-o page-ranges=pages option selects a range of pages for printing:

lp \-o page-ranges=1 filename ENTER
lp \-o page-ranges=1-4 filename ENTER
lp \-o page-ranges=1-4,7,9-12 filename ENTER
lpr \-o page-ranges=1-4,7,9-12 filename ENTER

As shown above, the pages value can be a single page, a range of pages, or a collection of page numbers and ranges separated by commas. The pages will always be printed in ascending order, regardless of the order of the pages in the page-ranges option.

The default is to print all pages.
Selecting Even or Odd Pages

Use the \-o page-set=set option to select the even or odd pages:

lp \-o page-set=odd filename ENTER
lp \-o page-set=even filename ENTER
lpr \-o page-set=even filename ENTER

The default is to print all pages.
Setting the Output Order

The the \-o outputorder=order option to set the output order of all pages:

lp \-o outputorder=normal filename ENTER
lp \-o outputorder=reverse filename ENTER
lpr \-o outputorder=reverse filename ENTER

N-Up Printing

The \-o number-up=value option selects N-Up printing. N-Up printing places multiple document pages on a single printed page. CUPS supports 1, 2, 4, 6, 9, and 16-Up formats; the default format is 1-Up:

lp \-o number-up=1 filename ENTER
lp \-o number-up=2 filename ENTER
lp \-o number-up=4 filename ENTER
lpr \-o number-up=16 filename ENTER

The \-o page-border=value option chooses the border to draw around each page:
* \-o page-border=double; draw two hairline borders around each page
* \-o page-border=double-thick; draw two 1pt borders around each page
* \-o page-border=none; do not draw a border (default)
* \-o page-border=single; draw one hairline border around each page
* \-o page-border=single-thick; draw one 1pt border around each page

The \-o number-up-layout=value option chooses the layout of the pages on each output page:
* \-o number-up-layout=btlr; Bottom to top, left to right
* \-o number-up-layout=btrl; Bottom to top, right to left
* \-o number-up-layout=lrbt; Left to right, bottom to top
* \-o number-up-layout=lrtb; Left to right, top to bottom (default)
* \-o number-up-layout=rlbt; Right to left, bottom to top
* \-o number-up-layout=rltb; Right to left, top to bottom
* \-o number-up-layout=tblr; Top to bottom, left to right
* \-o number-up-layout=tbrl; Top to bottom, right to left

Mirroring Prints

You can mirror a print using the \-o mirror option:

lp \-o mirror filename ENTER
lpr \-o mirror filename ENTER

This is useful for printing mirrored pages on transfer paper, for T shirts, mugs, etc.
Setting the Brightness

You can control the overall brightness of the printed output using the \-o brightness=percent option:

lp \-o brightness=120 filename ENTER
lpr \-o brightness=120 filename ENTER

Values greater than 100 will lighten the print, while values less than 100 will darken it.
Setting the Gamma Correction

You can control the overall gamma correction of the printed output using the \-o gamma=value option:

lp \-o gamma=1700 filename ENTER
lpr \-o gamma=1700 filename ENTER

Values greater than 1000 will lighten the print, while values less than 1000 will darken it. The default gamma is 1000.
Text Options

The following options apply when printing text files.
Setting the Number of Characters Per Inch

The \-o cpi=value option sets the number of characters per inch:

lp \-o cpi=10 filename ENTER
lp \-o cpi=12 filename ENTER
lpr \-o cpi=17 filename ENTER

The default characters per inch is 10.
Setting the Number of Lines Per Inch

The \-o lpi=value option sets the number of lines per inch:

lp \-o lpi=6 filename ENTER
lpr \-o lpi=8 filename ENTER

The default lines per inch is 6.
Setting the Number of Columns

The \-o columns=value option sets the number of text columns:

lp \-o columns=2 filename ENTER
lpr \-o columns=3 filename ENTER

The default number of columns is 1.
Setting the Page Margins

Normally the page margins are set to the hard limits of the printer. Use the \-o page-left=value, \-o page-right=value , \-o page-top=value, and \-o page-bottom=value options to adjust the page margins:

lp \-o page-left=value filename ENTER
lp \-o page-right=value filename ENTER
lp \-o page-top=value filename ENTER
lp \-o page-bottom=value filename ENTER
lpr \-o page-bottom=value filename ENTER

The value argument is the margin in points; each point is 1/72 inch or 0.35mm.
Pretty Printing

The \-o prettyprint option puts a header at the top of each page with the page number, job title (usually the filename), and the date. Also, C and C+\+ keywords are highlighted, and comment lines are italicized:

lp \-o prettyprint filename ENTER
lpr \-o prettyprint filename ENTER

Image Options

The following options apply when printing image files.
Positioning the Image

The \-o position=name option specifies the position of the image on the page:
* center - Center the image on the page (default)
* top - Print the image centered at the top of the page
* left - Print the image centered on the left of page
* right - Print the image centered on the right of the page
* top-left - Print the image at the top left corner of the page
* top-right - Print the image at the top right corner of the page
* bottom - Print the image centered at the bottom of the page
* bottom-left - Print the image at the bottom left corner of the page
* bottom-right - Print the image at the bottom right corner of the page

Scaling the Image

The \-o scaling=percent, \-o ppi=value, and \-o natural-scaling=percent options change the size of a printed image:

lp \-o scaling=percent filename ENTER
lp \-o ppi=value filename ENTER
lpr \-o natural-scaling=percent filename ENTER

The scaling=percent value is a number from 1 to 800 specifying the size in relation to the page (not the image.) A scaling of 100 percent will fill the page as completely as the image aspect ratio allows. A scaling of 200 percent will print on up to 4 pages.

The ppi=value value is a number from 1 to 1200 specifying the resolution of the image in pixels per inch. An image that is 3000x2400 pixels will print 10x8 inches at 300 pixels per inch, for example. If the specified resolution makes the image larger than the page, multiple pages will be printed to satisfy the request.

The natural-scaling=percent value is a number from 1 to 800 specifying the size in relation to the natural image size. A scaling of 100 percent will print the image at its natural size, while a scaling of 50 percent will print the image at half its natural size. If the specified scaling makes the image larger than the page, multiple pages will be printed to satisfy the request.
Adjusting the Hue (Tint) of an Image

The \-o hue=value option will adjust the hue of the printed image, much like the tint control on your television:

lp \-o hue=value filename ENTER
lpr \-o hue=value filename ENTER

The value argument is a number from \-360 to 360 and represents the color hue rotation. The following table summarizes the change you'll see with different colors:
Original	hue=-45	hue=45
Red	Purple	Yellow-orange
Green	Yellow-green	Blue-green
Yellow	Orange	Green-yellow
Blue	Sky-blue	Purple
Magenta	Indigo	Crimson
Cyan	Blue-green	Light-navy-blue

The default hue adjustment is 0.
Adjusting the Saturation (Color) of an Image

The \-o saturation=percent option adjusts the saturation of the colors in an image, much like the color knob on your television:

lp \-o saturation=percent filename ENTER
lpr \-o saturation=percent filename ENTER

The percent argument specifies the color saturation from 0 to 200. A color saturation of 0 produces a black-and-white print, while a value of 200 will make the colors extremely intense.

The default saturation is 100.
HP-GL/2 Options

The following options apply to HP-GL/2 files.
Printing in Black

The \-o blackplot option specifies that all pens should plot in black:

lp \-o blackplot filename ENTER
lpr \-o blackplot filename ENTER

The default is to use the colors defined in the plot file or the standard pen colors defined in the HP-GL/2 reference manual from Hewlett Packard.
Fitting the Plot on the Page

The \-o fitplot option specifies that the plot should be scaled to fit on the page:

lp \-o fitplot filename ENTER
lpr \-o fitplot filename ENTER

The default is to use the absolute distances specified in the plot file.
NOTE:

This feature depends upon an accurate plot size (PS) command in the HP-GL/2 file. If no plot size is given in the file than the HP-GL/2 filter assumes the plot is ANSI E size.

Setting the Default Pen Width

The \-o penwidth=value option specifies the default pen width for HP-GL/2 files:

lp \-o penwidth=value filename ENTER
lpr \-o penwidth=value filename ENTER

The pen width value specifies the pen width in micrometers. The default value of 1000 produces lines that are 1 millimeter in width. Specifying a pen width of 0 produces lines that are exactly 1 pixel wide.
NOTE:

This option is ignored when the pen widths are set in the plot file.

Raw or Unfiltered Output

The \-o raw option allows you to send files directly to a printer without filtering. This is sometimes required when printing from applications that provide their own "printer drivers" for your printer:

lp \-o raw filename ENTER
lpr \-o raw filename ENTER

The \-l option can also be used with the lpr command to send files directly to a printer:

lpr \-l filename ENTER

4 - Saving Printer Options and Defaults

This chapter describes how to save printer options for your printer and set your own default printer.
Printer Options

Each printer supports a large number of options, which you learned about in Chapter 3, "Standard Printer Options". Rather than specifying these options each time you print a file, CUPS allows you to save them as "default" options for the printer.

The lpoptions(1) command saves the options for your printers. Like the lp and lpr commands, it accepts printer options using the \-o argument:

lpoptions \-o prettyprint ENTER
lpoptions \-o media=A4 \-o sides=two-sided-long-edge ENTER
lpoptions \-o media=Legal \-o scaling=100 ENTER

Once saved, any lp or lpr command will use them when you print.
Note:

Running the lpoptions command as the root user (or any user with a UID of 0) will set the default options for all users. The root account does not have its own set of default options.

Setting Options for a Specific Printer

The previous example shows how to set the options for the default printer. The \-p printer option specifies the options are for another printer:

lpoptions \-p laserjet \-o prettyprint ENTER
lpoptions \-p laserjet \-o media=A4 \-o sides=two-sided-long-edge ENTER
lpoptions \-p deskjet \-o media=Legal \-o scaling=100 ENTER

Removing Options

The previous two examples shows how to set options for the default and a specific printer. Below, shows you how to remove the saved option using the \-r argument:

lpoptions \-r prettyprint ENTER
lpoptions \-p laserjet \-r prettyprint ENTER

Viewing the Current Defaults

The lpoptions command can also be used to show the current options by not specifying any new options on the command-line:

lpoptions ENTER
media=A4 sides=two-sided-long-edge
lpoptions \-p deskjet ENTER
media=Legal scaling=100

Viewing Options for a Specific Printer

You can display the supported options using the lpoptions command with the \-l option, as follows:

lpoptions \-p laserjet \-l ENTER

Setting the Default Printer

The administrator normally will set a system-wide default printer that is normally used as the default printer by everyone. Use the \-d printer option to set your own default printer:

lpoptions \-d deskjet ENTER

The printer can be local (deskjet) or remote ( deskjet@server).
Printer Instances

Besides setting options for each print queue, CUPS supports printer instances which allow you to define several different sets of options for each printer. You specify a printer instance using the slash (/) character:

lpoptions \-p laserjet/duplex \-o sides=two-sided-long-edge ENTER
lpoptions \-p laserjet/legal \-o media=Legal ENTER

The lp and lpr commands also understand this notation:

lp \-d laserjet/duplex filename ENTER
lpr \-P laserjet/legal filename ENTER

Removing Instances

Use the \-x printer/instance option to remove a printer instance that you no longer need:

lpoptions \-x laserjet ENTER
lpoptions \-x laserjet/duplex ENTER
lpoptions \-x laserjet/legal ENTER

The \-x option only removes the default options for that printer and instance; the original print queue will remain until deleted with the lpadmin(8) command by the administrator.
# Allow printing to printer MyLaserJet from
# itself and computers 192.10.2.5 and 192.10.2.6
&lt;Location /printers/MyLaserJet&gt;
...
Order deny,allow
Deny from all
Allow from 127.0.0.1
Allow from 192.10.2.5
Allow from 192.10.2.6
&lt;/Location&gt;

# Allow printing to printer MyLaserJet from
# itself and all computers on subnet 192.10.2.x
&lt;Location /printers/MyLaserJet&gt;
...
Order deny,allow
Deny from all
Allow from 127.0.0.1
Allow from 192.10.2.0/255.255.255.0
&lt;/Location&gt;</property>
    

<property name="body">CUPS Doc
To install cups and hplip on a new server, here is the procedure:

CUPS:
1\- ensure you have the following packages installed:
gcc, libjpeg, libjpeg-devel, libpng, libpng-devel, libtiff, libtiff-devel, zlib, zlib-devel,dbus-devel,php-devel,pyqt,pyqt-devel,xsane,net-snmp-devel

2\- Download the latest stable source from www.cups.org (1.3.6 as of this writing)

3\- Compile the source as follows:
{code}
rpmbuild -ta cups-version-source.tar.gz --without dbus
{code}
This will produce several compiled rpms in the /usr/src/redhat/RPMS/i386 directory.
The only ones you want are cups, cups-libs, cups-debuginfo, cups-devel,cups-lpd,cups-php
Do an rpm \-Uvh on all these packages.

HPLIP:
{code}
#tar -zxvf hplip-****.gz
#cd hplip-****
#(as banjobs, not ROOT) ./configure --enable-network-build --disable-pp-build --disable-fax-build --disable-gui-build --disable-scan-build --enable-doc-build --enable-foomatic-ppd-install --disable-foomatic-drv-install --with-hpppddir=/usr/share/cups/model/HP --disable-hpijs-only-build --prefix=/usr
#(as banjobs, not ROOT) make
#(as ROOT) make install
#/etc/init.d/hplip restart
{code}
The following command creates a print queue called tranb on Solaris
lpadmin \-p tranb \-v/dev/null \-m netstandard \-o dest=134.250.51.248:3002 \-T PS \-I postscript \-o protocol=tcp

\--landscape using LPR

lpr  \-o landscape \-o cpi=15 \-o lpi=12 \-o cpi=16 \-Pormond SHRTRTC_876.lis

Cups Options:

Jobs can also have options associated with them such as media size, number of copies, and priority.
CUPS supports collections of printers known as classes. Jobs sent to a class are forwarded to the first available printer in the class.
Filters allow a user or application to print many types of files without extra effort. Print jobs sent to a CUPS server are filtered before sending them to a printer.
Some filters convert job files to different formats that the printer can understand. Others perform page selection and ordering tasks.

CUPS provides filters for printing many types of image files, HP-GL/2 files, PDF files, and text files.
CUPS also supplies PostScript and image file Raster Image Processor ("RIP") filters that convert PostScript or image files into bitmaps that can be sent to a raster printer.

CUPS also provides implicit classes, which are collections of printers and/or classes with the same name. This allows you to setup multiple servers pointing to the same physical network printer,
for example, so that you aren't relying on a single system for printing.  Because this also works with printer classes, you can setup multiple servers and printers
and never worry about a single point of failure unless all of the printers and servers go down\!

General Options

The following options apply when printing all types of files.
Selecting the Media Size, Type, and Source

The \-o media=xyz option sets the media size, type, and/or source:

lp \-o media=Letter filename ENTER
lp \-o media=Letter,MultiPurpose filename ENTER
lpr \-o media=Letter,Transparency filename ENTER
lpr \-o media=Letter,MultiPurpose,Transparency filename ENTER

The available media sizes, types, and sources depend on the printer, but most support the following options (case is not significant):
* Letter - US Letter (8.5x11 inches, or 216x279mm)
* Legal - US Legal (8.5x14 inches, or 216x356mm)
* A4 - ISO A4 (8.27x11.69 inches, or 210x297mm)
* COM10 - US #10 Envelope (9.5x4.125 inches, or 241x105mm)
* DL - ISO DL Envelope (8.66x4.33 inches, or 220x110mm)
* Transparency - Transparency media type or source
* Upper - Upper paper tray
* Lower - Lower paper tray
* MultiPurpose - Multi-purpose paper tray
* LargeCapacity - Large capacity paper tray

The actual options supported are defined in the printer's PPD file in the PageSize, InputSlot, and MediaType options.
Setting the Orientation

The \-o landscape option will rotate the page 90 degrees to print in landscape orientation:

lp \-o landscape filename ENTER
lpr \-o landscape filename ENTER

Printing On Both Sides of the Paper

The \-o sides=two-sided-short-edge and \-o sides=two-sided-long-edge options will enable duplexing on the printer, if the printer supports it. The \-o sides=two-sided-short-edge option is suitable for landscape pages, while the \-o sides=two-sided-long-edge option is suitable for portrait pages:

lp \-o sides=two-sided-short-edge filename ENTER
lp \-o sides=two-sided-long-edge filename ENTER
lpr \-o sides=two-sided-long-edge filename ENTER

The default is to print single-sided:

lp \-o sides=one-sided filename ENTER
lpr \-o sides=one-sided filename ENTER

Banner Options

The following options apply when printing all types of files.
Selecting the Banner Page(s)

The \-o jobsheets=start,end option sets the banner page(s) to use for a job:

lp \-o job-sheets=none filename ENTER
lp \-o job-sheets=standard filename ENTER
lpr \-o job-sheets=classified,classified filename ENTER

If only one banner file is specified, it will be printed before the files in the job. If a second banner file is specified, it is printed after the files in the job.

The available banner pages depend on the local system configuration; CUPS includes the following banner files:
* none - Do not produce a banner page.
* classified - A banner page with a "classified" label at the top and bottom.
* confidential - A banner page with a "confidential" label at the top and bottom.
* secret - A banner page with a "secret" label at the top and bottom.
* standard - A banner page with no label at the top and bottom.
* topsecret - A banner page with a "top secret" label at the top and bottom.
* unclassified - A banner page with an "unclassified" label at the top and bottom.

Document Options

The following options apply when printing all types of files.
Selecting a Range of Pages

The \-o page-ranges=pages option selects a range of pages for printing:

lp \-o page-ranges=1 filename ENTER
lp \-o page-ranges=1-4 filename ENTER
lp \-o page-ranges=1-4,7,9-12 filename ENTER
lpr \-o page-ranges=1-4,7,9-12 filename ENTER

As shown above, the pages value can be a single page, a range of pages, or a collection of page numbers and ranges separated by commas. The pages will always be printed in ascending order, regardless of the order of the pages in the page-ranges option.

The default is to print all pages.
Selecting Even or Odd Pages

Use the \-o page-set=set option to select the even or odd pages:

lp \-o page-set=odd filename ENTER
lp \-o page-set=even filename ENTER
lpr \-o page-set=even filename ENTER

The default is to print all pages.
Setting the Output Order

The the \-o outputorder=order option to set the output order of all pages:

lp \-o outputorder=normal filename ENTER
lp \-o outputorder=reverse filename ENTER
lpr \-o outputorder=reverse filename ENTER

N-Up Printing

The \-o number-up=value option selects N-Up printing. N-Up printing places multiple document pages on a single printed page. CUPS supports 1, 2, 4, 6, 9, and 16-Up formats; the default format is 1-Up:

lp \-o number-up=1 filename ENTER
lp \-o number-up=2 filename ENTER
lp \-o number-up=4 filename ENTER
lpr \-o number-up=16 filename ENTER

The \-o page-border=value option chooses the border to draw around each page:
* \-o page-border=double; draw two hairline borders around each page
* \-o page-border=double-thick; draw two 1pt borders around each page
* \-o page-border=none; do not draw a border (default)
* \-o page-border=single; draw one hairline border around each page
* \-o page-border=single-thick; draw one 1pt border around each page

The \-o number-up-layout=value option chooses the layout of the pages on each output page:
* \-o number-up-layout=btlr; Bottom to top, left to right
* \-o number-up-layout=btrl; Bottom to top, right to left
* \-o number-up-layout=lrbt; Left to right, bottom to top
* \-o number-up-layout=lrtb; Left to right, top to bottom (default)
* \-o number-up-layout=rlbt; Right to left, bottom to top
* \-o number-up-layout=rltb; Right to left, top to bottom
* \-o number-up-layout=tblr; Top to bottom, left to right
* \-o number-up-layout=tbrl; Top to bottom, right to left

Mirroring Prints

You can mirror a print using the \-o mirror option:

lp \-o mirror filename ENTER
lpr \-o mirror filename ENTER

This is useful for printing mirrored pages on transfer paper, for T shirts, mugs, etc.
Setting the Brightness

You can control the overall brightness of the printed output using the \-o brightness=percent option:

lp \-o brightness=120 filename ENTER
lpr \-o brightness=120 filename ENTER

Values greater than 100 will lighten the print, while values less than 100 will darken it.
Setting the Gamma Correction

You can control the overall gamma correction of the printed output using the \-o gamma=value option:

lp \-o gamma=1700 filename ENTER
lpr \-o gamma=1700 filename ENTER

Values greater than 1000 will lighten the print, while values less than 1000 will darken it. The default gamma is 1000.
Text Options

The following options apply when printing text files.
Setting the Number of Characters Per Inch

The \-o cpi=value option sets the number of characters per inch:

lp \-o cpi=10 filename ENTER
lp \-o cpi=12 filename ENTER
lpr \-o cpi=17 filename ENTER

The default characters per inch is 10.
Setting the Number of Lines Per Inch

The \-o lpi=value option sets the number of lines per inch:

lp \-o lpi=6 filename ENTER
lpr \-o lpi=8 filename ENTER

The default lines per inch is 6.
Setting the Number of Columns

The \-o columns=value option sets the number of text columns:

lp \-o columns=2 filename ENTER
lpr \-o columns=3 filename ENTER

The default number of columns is 1.
Setting the Page Margins

Normally the page margins are set to the hard limits of the printer. Use the \-o page-left=value, \-o page-right=value , \-o page-top=value, and \-o page-bottom=value options to adjust the page margins:

lp \-o page-left=value filename ENTER
lp \-o page-right=value filename ENTER
lp \-o page-top=value filename ENTER
lp \-o page-bottom=value filename ENTER
lpr \-o page-bottom=value filename ENTER

The value argument is the margin in points; each point is 1/72 inch or 0.35mm.
Pretty Printing

The \-o prettyprint option puts a header at the top of each page with the page number, job title (usually the filename), and the date. Also, C and C+\+ keywords are highlighted, and comment lines are italicized:

lp \-o prettyprint filename ENTER
lpr \-o prettyprint filename ENTER

Image Options

The following options apply when printing image files.
Positioning the Image

The \-o position=name option specifies the position of the image on the page:
* center - Center the image on the page (default)
* top - Print the image centered at the top of the page
* left - Print the image centered on the left of page
* right - Print the image centered on the right of the page
* top-left - Print the image at the top left corner of the page
* top-right - Print the image at the top right corner of the page
* bottom - Print the image centered at the bottom of the page
* bottom-left - Print the image at the bottom left corner of the page
* bottom-right - Print the image at the bottom right corner of the page

Scaling the Image

The \-o scaling=percent, \-o ppi=value, and \-o natural-scaling=percent options change the size of a printed image:

lp \-o scaling=percent filename ENTER
lp \-o ppi=value filename ENTER
lpr \-o natural-scaling=percent filename ENTER

The scaling=percent value is a number from 1 to 800 specifying the size in relation to the page (not the image.) A scaling of 100 percent will fill the page as completely as the image aspect ratio allows. A scaling of 200 percent will print on up to 4 pages.

The ppi=value value is a number from 1 to 1200 specifying the resolution of the image in pixels per inch. An image that is 3000x2400 pixels will print 10x8 inches at 300 pixels per inch, for example. If the specified resolution makes the image larger than the page, multiple pages will be printed to satisfy the request.

The natural-scaling=percent value is a number from 1 to 800 specifying the size in relation to the natural image size. A scaling of 100 percent will print the image at its natural size, while a scaling of 50 percent will print the image at half its natural size. If the specified scaling makes the image larger than the page, multiple pages will be printed to satisfy the request.
Adjusting the Hue (Tint) of an Image

The \-o hue=value option will adjust the hue of the printed image, much like the tint control on your television:

lp \-o hue=value filename ENTER
lpr \-o hue=value filename ENTER

The value argument is a number from \-360 to 360 and represents the color hue rotation. The following table summarizes the change you'll see with different colors:
Original	hue=-45	hue=45
Red	Purple	Yellow-orange
Green	Yellow-green	Blue-green
Yellow	Orange	Green-yellow
Blue	Sky-blue	Purple
Magenta	Indigo	Crimson
Cyan	Blue-green	Light-navy-blue

The default hue adjustment is 0.
Adjusting the Saturation (Color) of an Image

The \-o saturation=percent option adjusts the saturation of the colors in an image, much like the color knob on your television:

lp \-o saturation=percent filename ENTER
lpr \-o saturation=percent filename ENTER

The percent argument specifies the color saturation from 0 to 200. A color saturation of 0 produces a black-and-white print, while a value of 200 will make the colors extremely intense.

The default saturation is 100.
HP-GL/2 Options

The following options apply to HP-GL/2 files.
Printing in Black

The \-o blackplot option specifies that all pens should plot in black:

lp \-o blackplot filename ENTER
lpr \-o blackplot filename ENTER

The default is to use the colors defined in the plot file or the standard pen colors defined in the HP-GL/2 reference manual from Hewlett Packard.
Fitting the Plot on the Page

The \-o fitplot option specifies that the plot should be scaled to fit on the page:

lp \-o fitplot filename ENTER
lpr \-o fitplot filename ENTER

The default is to use the absolute distances specified in the plot file.
NOTE:

This feature depends upon an accurate plot size (PS) command in the HP-GL/2 file. If no plot size is given in the file than the HP-GL/2 filter assumes the plot is ANSI E size.

Setting the Default Pen Width

The \-o penwidth=value option specifies the default pen width for HP-GL/2 files:

lp \-o penwidth=value filename ENTER
lpr \-o penwidth=value filename ENTER

The pen width value specifies the pen width in micrometers. The default value of 1000 produces lines that are 1 millimeter in width. Specifying a pen width of 0 produces lines that are exactly 1 pixel wide.
NOTE:

This option is ignored when the pen widths are set in the plot file.

Raw or Unfiltered Output

The \-o raw option allows you to send files directly to a printer without filtering. This is sometimes required when printing from applications that provide their own "printer drivers" for your printer:

lp \-o raw filename ENTER
lpr \-o raw filename ENTER

The \-l option can also be used with the lpr command to send files directly to a printer:

lpr \-l filename ENTER

4 - Saving Printer Options and Defaults

This chapter describes how to save printer options for your printer and set your own default printer.
Printer Options

Each printer supports a large number of options, which you learned about in Chapter 3, "Standard Printer Options". Rather than specifying these options each time you print a file, CUPS allows you to save them as "default" options for the printer.

The lpoptions(1) command saves the options for your printers. Like the lp and lpr commands, it accepts printer options using the \-o argument:

lpoptions \-o prettyprint ENTER
lpoptions \-o media=A4 \-o sides=two-sided-long-edge ENTER
lpoptions \-o media=Legal \-o scaling=100 ENTER

Once saved, any lp or lpr command will use them when you print.
Note:

Running the lpoptions command as the root user (or any user with a UID of 0) will set the default options for all users. The root account does not have its own set of default options.

Setting Options for a Specific Printer

The previous example shows how to set the options for the default printer. The \-p printer option specifies the options are for another printer:

lpoptions \-p laserjet \-o prettyprint ENTER
lpoptions \-p laserjet \-o media=A4 \-o sides=two-sided-long-edge ENTER
lpoptions \-p deskjet \-o media=Legal \-o scaling=100 ENTER

Removing Options

The previous two examples shows how to set options for the default and a specific printer. Below, shows you how to remove the saved option using the \-r argument:

lpoptions \-r prettyprint ENTER
lpoptions \-p laserjet \-r prettyprint ENTER

Viewing the Current Defaults

The lpoptions command can also be used to show the current options by not specifying any new options on the command-line:

lpoptions ENTER
media=A4 sides=two-sided-long-edge
lpoptions \-p deskjet ENTER
media=Legal scaling=100

Viewing Options for a Specific Printer

You can display the supported options using the lpoptions command with the \-l option, as follows:

lpoptions \-p laserjet \-l ENTER

Setting the Default Printer

The administrator normally will set a system-wide default printer that is normally used as the default printer by everyone. Use the \-d printer option to set your own default printer:

lpoptions \-d deskjet ENTER

The printer can be local (deskjet) or remote ( deskjet@server).
Printer Instances

Besides setting options for each print queue, CUPS supports printer instances which allow you to define several different sets of options for each printer. You specify a printer instance using the slash (/) character:

lpoptions \-p laserjet/duplex \-o sides=two-sided-long-edge ENTER
lpoptions \-p laserjet/legal \-o media=Legal ENTER

The lp and lpr commands also understand this notation:

lp \-d laserjet/duplex filename ENTER
lpr \-P laserjet/legal filename ENTER

Removing Instances

Use the \-x printer/instance option to remove a printer instance that you no longer need:

lpoptions \-x laserjet ENTER
lpoptions \-x laserjet/duplex ENTER
lpoptions \-x laserjet/legal ENTER

The \-x option only removes the default options for that printer and instance; the original print queue will remain until deleted with the lpadmin(8) command by the administrator.
# Allow printing to printer MyLaserJet from
# itself and computers 192.10.2.5 and 192.10.2.6
&lt;Location /printers/MyLaserJet&gt;
...
Order deny,allow
Deny from all
Allow from 127.0.0.1
Allow from 192.10.2.5
Allow from 192.10.2.6
&lt;/Location&gt;

# Allow printing to printer MyLaserJet from
# itself and all computers on subnet 192.10.2.x
&lt;Location /printers/MyLaserJet&gt;
...
Order deny,allow
Deny from all
Allow from 127.0.0.1
Allow from 192.10.2.0/255.255.255.0
&lt;/Location&gt;</property>
    

<property name="body">h1. Remove unnecessary services
{code:borderStyle=solid}
chkconfig --del anacron
chkconfig --del autofs
chkconfig --del apmd
chkconfig --del atd
chkconfig --del gpm
chkconfig --del irda
chkconfig --del isdn
chkconfig --del netfs
chkconfig --del nfs
chkconfig --del nfslock
chkconfig --del nscd
chkconfig --del ntpd
chkconfig --del portmap
chkconfig --del sendmail
chkconfig --del smartd
chkconfig --del snmpd
chkconfig --del snmptrapd
chkconfig --del winbind
chkconfig --del ypbind
cd /etc/xinetd.d/
rm -rf /etc/xinetd.d/chargen*
rm -rf /etc/xinetd.d/daytime*
rm -rf /etc/xinetd.d/echo*
rm -rf /etc/xinetd.d/rsync*
rm -rf /etc/xinetd.d/time*
{code}</property>
    

<property name="body">h1. The latest client for Windows and Linux can be found on the isengard FTP server in the Tivoli\Linux or Tivoli\Windoze directory

h2. Example contents of dsm.opt file
{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Example contents of dsm.sys file
{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMmethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu

nodename &lt;servernodename_goeshere&gt; ex. ASPEN
passwordaccess generate
MANAGEDSERVICES	schedule webclient

exclude     /.../core
exclude     /.../tmp/.../*
exclude.dir /proc
exclude.dir /proc/
exclude.dir /dev
exclude.dir /dev/
exclude.dir	/mnt
exclude.dir	/mnt/
exclude.dir /usr/share/man
exclude dsmsched.log
{code}

h2. Configuring Automatic Startup
h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:
{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}
h4. Next, execute the following commands:
{code}
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}
h4. Finally, you must start the daemon manually and enter the password; this is only required once- it will remember it going forward
At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc i
#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.
{code}
Tivoli Upgrade Fix:

Upgrading Tivoli frequently breaks itself; this is the process to fix it after the fact.

1- Install the latest RPMS

2- Make soft links in the /usr/lib directory to all the .so files in /opt/tivoli/tsm/client/api/bin folder
cd /usr/lib
ln -s /opt/tivoli/tsm/client/api/bin/libct_cu.so libct_cu.so
ln -s /opt/tivoli/tsm/client/api/bin/libdmapi.so libdmapi.so
ln -s /opt/tivoli/tsm/client/api/bin/libgpfs.so libgpfs.so
ln -s /opt/tivoli/tsm/client/api/bin/libha_gs_r.so libha_gs_r.so
ln -s /opt/tivoli/tsm/client/api/bin/libxerces-c1_6_0.so libxerces-c1_6_0.so
ln -s /opt/tivoli/tsm/client/api/bin/libxmlutil-5.4.1.0.so libxmlutil-5.4.1.0.so


3- Make a soft link in the /opt/tivoli/tsm/client/ba/bin folder to /opt/tivoli/tsm/client/lang/en_US
ln -s /opt/tivoli/tsm/client/lang/en_US/ en_US

4- Stop and Start the process.
{code}</property>
    

<property name="body">h1. The latest client for Windows and Linux can be found on the isengard FTP server in the Tivoli\Linux or Tivoli\Windoze directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Example contents of dsm.sys file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMmethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu

nodename &lt;servernodename_goeshere&gt; ex. ASPEN
passwordaccess generate
MANAGEDSERVICES	schedule webclient

exclude     /.../core
exclude     /.../tmp/.../*
exclude.dir /proc
exclude.dir /proc/
exclude.dir /dev
exclude.dir /dev/
exclude.dir	/mnt
exclude.dir	/mnt/
exclude.dir /usr/share/man
exclude dsmsched.log
{code}

h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc i
#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.

{code}
Tivoli Upgrade Fix:

Upgrading Tivoli frequently breaks itself; this is the process to fix it after the fact.

1- Install the latest RPMS

2- Make soft links in the /usr/lib directory to all the .so files in /opt/tivoli/tsm/client/api/bin folder
cd /usr/lib
ln -s /opt/tivoli/tsm/client/api/bin/libct_cu.so libct_cu.so
ln -s /opt/tivoli/tsm/client/api/bin/libdmapi.so libdmapi.so
ln -s /opt/tivoli/tsm/client/api/bin/libgpfs.so libgpfs.so
ln -s /opt/tivoli/tsm/client/api/bin/libha_gs_r.so libha_gs_r.so
ln -s /opt/tivoli/tsm/client/api/bin/libxerces-c1_6_0.so libxerces-c1_6_0.so
ln -s /opt/tivoli/tsm/client/api/bin/libxmlutil-5.4.1.0.so libxmlutil-5.4.1.0.so


3- Make a soft link in the /opt/tivoli/tsm/client/ba/bin folder to /opt/tivoli/tsm/client/lang/en_US
ln -s /opt/tivoli/tsm/client/lang/en_US/ en_US

4- Stop and Start the process.
{code}
This section added for Ubuntu:For those of you who have seen this before, I've corrected a couple of
errors in it.

I recently built up a linux box using Ubuntu and discovered that it's
not hard to set it up to use the TSM backup client.  Assuming you have
a passing familiarity with setting up TSM on RPM-based distributions,
here are the basic steps:

1. Install the "alien" package which lets you (among other things)
install RPM packages on Ubuntu or other Debian-based distros.

    $ sudo apt-get install alien

2.  download the TSM client software from IBM using your web browser.

3.  untar the TSM RPMs...

4.  Use alien to install the appropriate RPMs.

    $ sudo alien -i --scripts TIVsm-API.i386.rpm TIVsm-BA.i386.rpm

5.  Set up the normal TSM configuration (dsm.opt, dsm.sys, inclexcl.dsm).

6.  Run a manual backup.

     $ sudo dsmc incremental

7.  open port 1501 to the backup server in your firewall.

8.  Ubuntu uses Upstart instead of inittabs.  To add dsm to the
configuration, create a /etc/event.d/dsm-sched file containing:

-----------------------  /etc/event.d/dsm-sched -----------------------
# dsm-sched
#
# This service starts the Tivoli Storage Manager "dsmc sched" backup
# process and respawns it as the scheduled backup happens or the
# dsmc process gets killed or dies.

start on runlevel 2
start on runlevel 3
start on runlevel 4
start on runlevel 5

stop on runlevel 0
stop on runlevel 1
stop on runlevel 6

respawn
exec /usr/bin/dsmc sched &gt;/dev/null 2&gt;&amp;1
-----------------------  end /etc/event.d/dsm-sched ----------------------------

9.  Start the dsmc sched process

     $ sudo start dsm-sched

10.  Check to see if the /var/log/dsmsched.log is correct.

     $ tail /var/log/dsmsched.log

06/29/07   13:33:13 --- SCHEDULEREC QUERY END
06/29/07   13:33:13 Next operation scheduled:
06/29/07   13:33:13 ------------------------------------------------------------
06/29/07   13:33:13 Schedule Name:         AM0230
06/29/07   13:33:13 Action:                Incremental
06/29/07   13:33:13 Objects:
06/29/07   13:33:13 Options:
06/29/07   13:33:13 Server Window Start:   02:30:00 on 06/30/07
06/29/07   13:33:13 ------------------------------------------------------------
06/29/07   13:33:13 Waiting to be contacted by the server.


11.  If you wish to use the dsmj GUI, you must also install a Java
runtime environment.  There are several of these available, and JREs
are backwards compatible.

  $ sudo apt-get install sun-java6-bin

Note that the dsmj seems to want to run with root permissions.  To run it, use:

  $ sudo dsmj


\\</property>
    

<property name="body">&lt;ac:structured-macro ac:macro-id="0b8aa59c-099c-41a4-a993-af61a5605219" ac:name="attachments" ac:schema-version="1"&gt;&lt;ac:parameter ac:name="old"&gt;true&lt;/ac:parameter&gt;&lt;/ac:structured-macro&gt;</property>
    

<property name="body">h1. The latest client for Windows and Linux can be found on the isengard FTP server in the Tivoli\Linux or Tivoli\Windoze directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Example contents of dsm.sys file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMmethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu

nodename &lt;servernodename_goeshere&gt; ex. ASPEN
passwordaccess generate
MANAGEDSERVICES	schedule webclient

exclude     /.../core
exclude     /.../tmp/.../*
exclude.dir /proc
exclude.dir /proc/
exclude.dir /dev
exclude.dir /dev/
exclude.dir	/mnt
exclude.dir	/mnt/
exclude.dir /usr/share/man
exclude dsmsched.log
{code}

h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc i
#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.

{code}
Tivoli Upgrade Fix:

Upgrading Tivoli frequently breaks itself; this is the process to fix it after the fact.

1- Install the latest RPMS

2- Make soft links in the /usr/lib directory to all the .so files in /opt/tivoli/tsm/client/api/bin folder
cd /usr/lib
ln -s /opt/tivoli/tsm/client/api/bin/libct_cu.so libct_cu.so
ln -s /opt/tivoli/tsm/client/api/bin/libdmapi.so libdmapi.so
ln -s /opt/tivoli/tsm/client/api/bin/libgpfs.so libgpfs.so
ln -s /opt/tivoli/tsm/client/api/bin/libha_gs_r.so libha_gs_r.so
ln -s /opt/tivoli/tsm/client/api/bin/libxerces-c1_6_0.so libxerces-c1_6_0.so
ln -s /opt/tivoli/tsm/client/api/bin/libxmlutil-5.4.1.0.so libxmlutil-5.4.1.0.so


3- Make a soft link in the /opt/tivoli/tsm/client/ba/bin folder to /opt/tivoli/tsm/client/lang/en_US
ln -s /opt/tivoli/tsm/client/lang/en_US/ en_US

4- Stop and Start the process.
{code}
This section added for Ubuntu:For those of you who have seen this before, I've corrected a couple of
errors in it.

I recently built up a linux box using Ubuntu and discovered that it's
not hard to set it up to use the TSM backup client.  Assuming you have
a passing familiarity with setting up TSM on RPM-based distributions,
here are the basic steps:

1. Install the "alien" package which lets you (among other things)
install RPM packages on Ubuntu or other Debian-based distros.

$ sudo apt-get install alien

2.  download the TSM client software from IBM using your web browser.

3.  untar the TSM RPMs...

4.  Use alien to install the appropriate RPMs.

$ sudo alien \-i \--scripts TIVsm-API.i386.rpm TIVsm-BA.i386.rpm

5.  Set up the normal TSM configuration (dsm.opt, dsm.sys, inclexcl.dsm).

6.  Run a manual backup.

$ sudo dsmc incremental

7.  open port 1501 to the backup server in your firewall.

8.  Ubuntu uses Upstart instead of inittabs.  To add dsm to the
configuration, create a /etc/event.d/dsm-sched file containing:

\----------------------\-  /etc/event.d/dsm-sched \----------------------\-
{code}
#dsm-sched
# This service starts the Tivoli Storage Manager "dsmc sched" backup
# process and respawns it as the scheduled backup happens or the
# dsmc process gets killed or dies.

start on runlevel 2
start on runlevel 3
start on runlevel 4
start on runlevel 5

stop on runlevel 0
stop on runlevel 1
stop on runlevel 6

respawn
exec /usr/bin/dsmc sched &gt;/dev/null 2&gt;&amp;1
{code}
\----------------------\-  end /etc/event.d/dsm-sched \---------------------------\-

9.  Start the dsmc sched process

$ sudo start dsm-sched

10.  Check to see if the /var/log/dsmsched.log is correct.

$ tail /var/log/dsmsched.log

06/29/07   13:33:13 --- SCHEDULEREC QUERY END
06/29/07   13:33:13 Next operation scheduled:
06/29/07   13:33:13 \-----------------------------------------------------------\-
06/29/07   13:33:13 Schedule Name:         AM0230
06/29/07   13:33:13 Action:                Incremental
06/29/07   13:33:13 Objects:
06/29/07   13:33:13 Options:
06/29/07   13:33:13 Server Window Start:   02:30:00 on 06/30/07
06/29/07   13:33:13 \-----------------------------------------------------------\-
06/29/07   13:33:13 Waiting to be contacted by the server.

11.  If you wish to use the dsmj GUI, you must also install a Java
runtime environment.  There are several of these available, and JREs
are backwards compatible.

$ sudo apt-get install sun-java6-bin

Note that the dsmj seems to want to run with root permissions.  To run it, use:

$ sudo dsmj

\\</property>
    

<property name="body">h1. The latest client for Windows and Linux can be found on the isengard FTP server in the Tivoli\Linux or Tivoli\Windoze directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Example contents of dsm.sys file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMmethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu

nodename &lt;servernodename_goeshere&gt; ex. ASPEN
passwordaccess generate
MANAGEDSERVICES	schedule webclient

exclude     /.../core
exclude     /.../tmp/.../*
exclude.dir /proc
exclude.dir /proc/
exclude.dir /dev
exclude.dir /dev/
exclude.dir	/mnt
exclude.dir	/mnt/
exclude.dir /usr/share/man
exclude dsmsched.log
{code}

h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc i
#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to either make soft links in the /usr/lib directory to all the .so files in /opt/tivoli/tsm/client/api/bin folder
{code}
cd /usr/lib
ln -s /opt/tivoli/tsm/client/api/bin/libct_cu.so libct_cu.so
ln -s /opt/tivoli/tsm/client/api/bin/libdmapi.so libdmapi.so
ln -s /opt/tivoli/tsm/client/api/bin/libgpfs.so libgpfs.so
ln -s /opt/tivoli/tsm/client/api/bin/libha_gs_r.so libha_gs_r.so
ln -s /opt/tivoli/tsm/client/api/bin/libxerces-c1_6_0.so libxerces-c1_6_0.so
ln -s /opt/tivoli/tsm/client/api/bin/libxmlutil-5.4.1.0.so libxmlutil-5.4.1.0.so
{code}
or, a perhaps easier alternative, is to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin/
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Notes

This section added for Ubuntu:For those of you who have seen this before, I've corrected a couple of
errors in it.

I recently built up a linux box using Ubuntu and discovered that it's
not hard to set it up to use the TSM backup client.  Assuming you have
a passing familiarity with setting up TSM on RPM-based distributions,
here are the basic steps:

1. Install the "alien" package which lets you (among other things)
install RPM packages on Ubuntu or other Debian-based distros.

$ sudo apt-get install alien

2.  download the TSM client software from IBM using your web browser.

3.  untar the TSM RPMs...

4.  Use alien to install the appropriate RPMs.

$ sudo alien \-i \--scripts TIVsm-API.i386.rpm TIVsm-BA.i386.rpm

5.  Set up the normal TSM configuration (dsm.opt, dsm.sys, inclexcl.dsm).

6.  Run a manual backup.

$ sudo dsmc incremental

7.  open port 1501 to the backup server in your firewall.

8.  Ubuntu uses Upstart instead of inittabs.  To add dsm to the
configuration, create a /etc/event.d/dsm-sched file containing:

\----------------\--\--\--\-  /etc/event.d/dsm-sched \--\--\------------------\-
{code}
#dsm-sched
# This service starts the Tivoli Storage Manager "dsmc sched" backup
# process and respawns it as the scheduled backup happens or the
# dsmc process gets killed or dies.

start on runlevel 2
start on runlevel 3
start on runlevel 4
start on runlevel 5

stop on runlevel 0
stop on runlevel 1
stop on runlevel 6

respawn
exec /usr/bin/dsmc sched &gt;/dev/null 2&gt;&amp;1
{code}
\----------------\--\--\--\-  end /etc/event.d/dsm-sched \--\--\-----------------------\-

9.  Start the dsmc sched process

$ sudo start dsm-sched

10.  Check to see if the /var/log/dsmsched.log is correct.

$ tail /var/log/dsmsched.log

06/29/07   13:33:13 --- SCHEDULEREC QUERY END
06/29/07   13:33:13 Next operation scheduled:
06/29/07   13:33:13 \-----------------------------------------------------------\-
06/29/07   13:33:13 Schedule Name:         AM0230
06/29/07   13:33:13 Action:                Incremental
06/29/07   13:33:13 Objects:
06/29/07   13:33:13 Options:
06/29/07   13:33:13 Server Window Start:   02:30:00 on 06/30/07
06/29/07   13:33:13 \-----------------------------------------------------------\-
06/29/07   13:33:13 Waiting to be contacted by the server.

11.  If you wish to use the dsmj GUI, you must also install a Java
runtime environment.  There are several of these available, and JREs
are backwards compatible.

$ sudo apt-get install sun-java6-bin

Note that the dsmj seems to want to run with root permissions.  To run it, use:

$ sudo dsmj

\\</property>
    

<property name="body">h1. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Example contents of dsm.sys file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMmethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu

nodename &lt;servernodename_goeshere&gt; ex. ASPEN
passwordaccess generate
MANAGEDSERVICES	schedule webclient

exclude     /.../core
exclude     /.../tmp/.../*
exclude.dir /proc
exclude.dir /proc/
exclude.dir /dev
exclude.dir /dev/
exclude.dir	/mnt
exclude.dir	/mnt/
exclude.dir /usr/share/man
exclude dsmsched.log
{code}

h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc i
#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to either make soft links in the /usr/lib directory to all the .so files in /opt/tivoli/tsm/client/api/bin folder
{code}
cd /usr/lib
ln -s /opt/tivoli/tsm/client/api/bin/libct_cu.so libct_cu.so
ln -s /opt/tivoli/tsm/client/api/bin/libdmapi.so libdmapi.so
ln -s /opt/tivoli/tsm/client/api/bin/libgpfs.so libgpfs.so
ln -s /opt/tivoli/tsm/client/api/bin/libha_gs_r.so libha_gs_r.so
ln -s /opt/tivoli/tsm/client/api/bin/libxerces-c1_6_0.so libxerces-c1_6_0.so
ln -s /opt/tivoli/tsm/client/api/bin/libxmlutil-5.4.1.0.so libxmlutil-5.4.1.0.so
{code}
or, a perhaps easier alternative, is to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin/
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Notes

This section added for Ubuntu:For those of you who have seen this before, I've corrected a couple of
errors in it.

I recently built up a linux box using Ubuntu and discovered that it's
not hard to set it up to use the TSM backup client.  Assuming you have
a passing familiarity with setting up TSM on RPM-based distributions,
here are the basic steps:

1. Install the "alien" package which lets you (among other things)
install RPM packages on Ubuntu or other Debian-based distros.

$ sudo apt-get install alien

2.  download the TSM client software from IBM using your web browser.

3.  untar the TSM RPMs...

4.  Use alien to install the appropriate RPMs.

$ sudo alien \-i \--scripts TIVsm-API.i386.rpm TIVsm-BA.i386.rpm

5.  Set up the normal TSM configuration (dsm.opt, dsm.sys, inclexcl.dsm).

6.  Run a manual backup.

$ sudo dsmc incremental

7.  open port 1501 to the backup server in your firewall.

8.  Ubuntu uses Upstart instead of inittabs.  To add dsm to the
configuration, create a /etc/event.d/dsm-sched file containing:

\--------------\--\--\--\--\-  /etc/event.d/dsm-sched --\--\------------------\-
{code}
#dsm-sched
# This service starts the Tivoli Storage Manager "dsmc sched" backup
# process and respawns it as the scheduled backup happens or the
# dsmc process gets killed or dies.

start on runlevel 2
start on runlevel 3
start on runlevel 4
start on runlevel 5

stop on runlevel 0
stop on runlevel 1
stop on runlevel 6

respawn
exec /usr/bin/dsmc sched &gt;/dev/null 2&gt;&amp;1
{code}
\--------------\--\--\--\--\-  end /etc/event.d/dsm-sched --\--\-----------------------\-

9.  Start the dsmc sched process

$ sudo start dsm-sched

10.  Check to see if the /var/log/dsmsched.log is correct.

$ tail /var/log/dsmsched.log

06/29/07   13:33:13 --- SCHEDULEREC QUERY END
06/29/07   13:33:13 Next operation scheduled:
06/29/07   13:33:13 \-----------------------------------------------------------\-
06/29/07   13:33:13 Schedule Name:         AM0230
06/29/07   13:33:13 Action:                Incremental
06/29/07   13:33:13 Objects:
06/29/07   13:33:13 Options:
06/29/07   13:33:13 Server Window Start:   02:30:00 on 06/30/07
06/29/07   13:33:13 \-----------------------------------------------------------\-
06/29/07   13:33:13 Waiting to be contacted by the server.

11.  If you wish to use the dsmj GUI, you must also install a Java
runtime environment.  There are several of these available, and JREs
are backwards compatible.

$ sudo apt-get install sun-java6-bin

Note that the dsmj seems to want to run with root permissions.  To run it, use:

$ sudo dsmj

\\</property>
    

<property name="body">h1. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Example contents of dsm.sys file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMmethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu

nodename &lt;servernodename_goeshere&gt; ex. ASPEN
passwordaccess generate
MANAGEDSERVICES	schedule webclient

exclude     /.../core
exclude     /.../tmp/.../*
exclude.dir /proc
exclude.dir /proc/
exclude.dir /dev
exclude.dir /dev/
exclude.dir	/mnt
exclude.dir	/mnt/
exclude.dir /usr/share/man
exclude dsmsched.log
{code}

h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc i
#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to either make soft links in the /usr/lib directory to all the .so files in /opt/tivoli/tsm/client/api/bin folder
{code}
cd /usr/lib
ln -s /opt/tivoli/tsm/client/api/bin/libct_cu.so libct_cu.so
ln -s /opt/tivoli/tsm/client/api/bin/libdmapi.so libdmapi.so
ln -s /opt/tivoli/tsm/client/api/bin/libgpfs.so libgpfs.so
ln -s /opt/tivoli/tsm/client/api/bin/libha_gs_r.so libha_gs_r.so
ln -s /opt/tivoli/tsm/client/api/bin/libxerces-c1_6_0.so libxerces-c1_6_0.so
ln -s /opt/tivoli/tsm/client/api/bin/libxmlutil-5.4.1.0.so libxmlutil-5.4.1.0.so
{code}
or, a perhaps easier alternative, is to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Notes

This section added for Ubuntu:For those of you who have seen this before, I've corrected a couple of
errors in it.

I recently built up a linux box using Ubuntu and discovered that it's
not hard to set it up to use the TSM backup client.  Assuming you have
a passing familiarity with setting up TSM on RPM-based distributions,
here are the basic steps:

1. Install the "alien" package which lets you (among other things)
install RPM packages on Ubuntu or other Debian-based distros.

$ sudo apt-get install alien

2.  download the TSM client software from IBM using your web browser.

3.  untar the TSM RPMs...

4.  Use alien to install the appropriate RPMs.

$ sudo alien \-i \--scripts TIVsm-API.i386.rpm TIVsm-BA.i386.rpm

5.  Set up the normal TSM configuration (dsm.opt, dsm.sys, inclexcl.dsm).

6.  Run a manual backup.

$ sudo dsmc incremental

7.  open port 1501 to the backup server in your firewall.

8.  Ubuntu uses Upstart instead of inittabs.  To add dsm to the
configuration, create a /etc/event.d/dsm-sched file containing:

\------------\--\--\--\--\--\-  /etc/event.d/dsm-sched \--\--\------------------\-
{code}
#dsm-sched
# This service starts the Tivoli Storage Manager "dsmc sched" backup
# process and respawns it as the scheduled backup happens or the
# dsmc process gets killed or dies.

start on runlevel 2
start on runlevel 3
start on runlevel 4
start on runlevel 5

stop on runlevel 0
stop on runlevel 1
stop on runlevel 6

respawn
exec /usr/bin/dsmc sched &gt;/dev/null 2&gt;&amp;1
{code}
\------------\--\--\--\--\--\-  end /etc/event.d/dsm-sched \--\--\-----------------------\-

9.  Start the dsmc sched process

$ sudo start dsm-sched

10.  Check to see if the /var/log/dsmsched.log is correct.

$ tail /var/log/dsmsched.log

06/29/07   13:33:13 --- SCHEDULEREC QUERY END
06/29/07   13:33:13 Next operation scheduled:
06/29/07   13:33:13 \-----------------------------------------------------------\-
06/29/07   13:33:13 Schedule Name:         AM0230
06/29/07   13:33:13 Action:                Incremental
06/29/07   13:33:13 Objects:
06/29/07   13:33:13 Options:
06/29/07   13:33:13 Server Window Start:   02:30:00 on 06/30/07
06/29/07   13:33:13 \-----------------------------------------------------------\-
06/29/07   13:33:13 Waiting to be contacted by the server.

11.  If you wish to use the dsmj GUI, you must also install a Java
runtime environment.  There are several of these available, and JREs
are backwards compatible.

$ sudo apt-get install sun-java6-bin

Note that the dsmj seems to want to run with root permissions.  To run it, use:

$ sudo dsmj

\\</property>
    

<property name="body" />
    

<property name="body">h1. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Example contents of dsm.sys file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMmethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu

nodename &lt;servernodename_goeshere&gt; ex. ASPEN
passwordaccess generate
MANAGEDSERVICES	schedule webclient

exclude     /.../core
exclude     /.../tmp/.../*
exclude.dir /proc
exclude.dir /proc/
exclude.dir /dev
exclude.dir /dev/
exclude.dir	/mnt
exclude.dir	/mnt/
exclude.dir /usr/share/man
exclude dsmsched.log
{code}

h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc i
#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Notes

This section added for Ubuntu:For those of you who have seen this before, I've corrected a couple of
errors in it.

I recently built up a linux box using Ubuntu and discovered that it's
not hard to set it up to use the TSM backup client.  Assuming you have
a passing familiarity with setting up TSM on RPM-based distributions,
here are the basic steps:

1. Install the "alien" package which lets you (among other things)
install RPM packages on Ubuntu or other Debian-based distros.

$ sudo apt-get install alien

2.  download the TSM client software from IBM using your web browser.

3.  untar the TSM RPMs...

4.  Use alien to install the appropriate RPMs.

$ sudo alien \-i \--scripts TIVsm-API.i386.rpm TIVsm-BA.i386.rpm

5.  Set up the normal TSM configuration (dsm.opt, dsm.sys, inclexcl.dsm).

6.  Run a manual backup.

$ sudo dsmc incremental

7.  open port 1501 to the backup server in your firewall.

8.  Ubuntu uses Upstart instead of inittabs.  To add dsm to the
configuration, create a /etc/event.d/dsm-sched file containing:

\----------\--\--\--\--\--\--\-  /etc/event.d/dsm-sched --\--\------------------\-
{code}
#dsm-sched
# This service starts the Tivoli Storage Manager "dsmc sched" backup
# process and respawns it as the scheduled backup happens or the
# dsmc process gets killed or dies.

start on runlevel 2
start on runlevel 3
start on runlevel 4
start on runlevel 5

stop on runlevel 0
stop on runlevel 1
stop on runlevel 6

respawn
exec /usr/bin/dsmc sched &gt;/dev/null 2&gt;&amp;1
{code}
\----------\--\--\--\--\--\--\-  end /etc/event.d/dsm-sched --\--\-----------------------\-

9.  Start the dsmc sched process

$ sudo start dsm-sched

10.  Check to see if the /var/log/dsmsched.log is correct.

$ tail /var/log/dsmsched.log

06/29/07   13:33:13 --- SCHEDULEREC QUERY END
06/29/07   13:33:13 Next operation scheduled:
06/29/07   13:33:13 \-----------------------------------------------------------\-
06/29/07   13:33:13 Schedule Name:         AM0230
06/29/07   13:33:13 Action:                Incremental
06/29/07   13:33:13 Objects:
06/29/07   13:33:13 Options:
06/29/07   13:33:13 Server Window Start:   02:30:00 on 06/30/07
06/29/07   13:33:13 \-----------------------------------------------------------\-
06/29/07   13:33:13 Waiting to be contacted by the server.

11.  If you wish to use the dsmj GUI, you must also install a Java
runtime environment.  There are several of these available, and JREs
are backwards compatible.

$ sudo apt-get install sun-java6-bin

Note that the dsmj seems to want to run with root permissions.  To run it, use:

$ sudo dsmj

\\</property>
    

<property name="body">&lt;h3&gt;Create a file called suu_startup in the /etc/init.d directory.  Be sure to replace &amp;lt;server&amp;gt; with your server's name, i.e. oak, aspen, etc. Save file and proceed to next steps.&lt;/h3&gt;

&lt;ac:structured-macro ac:macro-id="1ec53806-71ac-45f7-8f38-e797e706898c" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
#!/bin/bash
#
# chkconfig: 35 98 01
# description: Starts Oracle Application Server software
#

export SOURCE=/u01/app/oracle/scripts
export USER=root
touch /var/lock/subsys/suu_startup
case "$1" in
start)
        echo -n "Starting suu_startup"

        if [ -f "$SOURCE/start&lt;server&gt;.ksh" ]; then
                $SOURCE/start&lt;server&gt;.ksh #&gt; /tmp/start&lt;server&gt;.log 2&gt;&amp;1
        fi
        ;;
stop)
        echo -n "Stopping suu_startup"

        if [ -f "$SOURCE/stop&lt;server&gt;.ksh" ]; then
                $SOURCE/stop&lt;server&gt;.ksh #&gt; /tmp/stop&lt;server&gt;.log 2&gt;&amp;1
        fi
        ;;
*)
        printf "Usage: `basename $0` {start | stop}\n"
        exit 1
        ;;
esac

exit 0
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;

&lt;h4&gt;Step 2 - chmod 755 suu_startup&lt;/h4&gt;
&lt;h4&gt;Step 3 - chkconfig --add suu_startup&lt;/h4&gt;
&lt;h4&gt;Step 4 - chkconfig --level 345 suu_startup on&lt;/h4&gt;</property>
    

<property name="body">h3. Be sure to replace &lt;server&gt; with your server's name, i.e. oak, aspen, etc.

{code}
#!/bin/bash
#
# chkconfig: 35 98 01
# description: Starts Oracle Application Server software
#

export SOURCE=/u01/app/oracle/scripts
export USER=root
touch /var/lock/subsys/suu_startup
case "$1" in
start)
        echo -n "Starting suu_startup"

        if [ -f "$SOURCE/start&lt;server&gt;.ksh" ]; then
                $SOURCE/start&lt;server&gt;.ksh #&gt; /tmp/start&lt;server&gt;.log 2&gt;&amp;1
        fi
        ;;
stop)
        echo -n "Stopping suu_startup"

        if [ -f "$SOURCE/stop&lt;server&gt;.ksh" ]; then
                $SOURCE/stop&lt;server&gt;.ksh #&gt; /tmp/stop&lt;server&gt;.log 2&gt;&amp;1
        fi
        ;;
*)
        printf "Usage: `basename $0` {start | stop}\n"
        exit 1
        ;;
esac

exit 0
{code}</property>
    

<property name="body">&lt;p&gt;First off, do not use Tomcat from the Ubuntu repository - download it yourself, and extract it in the home directory of the user it will run as.  The example given here is from our xmlbill server.&lt;/p&gt;

&lt;h2&gt;Tomcat Startup Script&lt;/h2&gt;

&lt;h5&gt;Step 1: To make Tomcat start automatically, you must create a file in /etc/init.d called tomcat.  Populate the file with the following:&lt;/h5&gt;
&lt;ac:structured-macro ac:macro-id="a71495cc-57b2-4302-89a4-28673aa44970" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
#!/bin/bash
#
# Startup script for Tomcat server
#
# chkconfig: - 83 53
# description: Starts and stops the Tomcat daemon.
# processname: tomcat
# pidfile: /var/run/tomcat.pid
export JAVA_HOME=/usr/lib/jvm/java-6-sun
export TOMCAT_HOME=/home/billservice/apps/apache-tomcat-6.0.18
export TOMCAT_USER=billservice

# See how we were called.
case $1 in
        start)

su - $TOMCAT_USER -c "sh $TOMCAT_HOME/bin/startup.sh"
        ;;
        stop)
su - $TOMCAT_USER -c "sh $TOMCAT_HOME/bin/shutdown.sh"
        ;;
        restart)
su - $TOMCAT_USER -c "sh $TOMCAT_HOME/bin/shutdown.sh"
su - $TOMCAT_USER -c "sh $TOMCAT_HOME/bin/startup.sh"
        ;;
        *)
                echo "Usage: /etc/init.d/tomcat start|stop|restart"
        ;;
esac

exit 0
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;

&lt;p&gt;A couple of things to note here; we 'su' to the user we want the process to run as.  This is important because we do NOT want processes running as root.  Additionally, we are explicitly setting the JAVA_HOME environment variable here, but you may wish to set it in /etc/profile (system-wide) or ~.bashrc (user-specific).&lt;/p&gt;

&lt;h5&gt;Set to start automatically&lt;/h5&gt;
&lt;p&gt;Run the following commands as root:&lt;/p&gt;
&lt;ac:structured-macro ac:macro-id="91ad35ee-de98-44cf-a181-b761c4ad57f1" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
#chmod 755 /etc/init.d/tomcat
#update-rc.d tomcat defaults
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;
&lt;p&gt;That's it; reboot to verify that everything starts the way you expect.&lt;/p&gt;</property>
    

<property name="body">First off, do not use Tomcat from the Ubuntu repository - download it yourself, and extract it in the home directory of the user it will run as.</property>
    

<property name="body">First off, do not use Tomcat from the Ubuntu repository - download it yourself, and extract it in the home directory of the user it will run as.  The example given here is from our xmlbill server.

To make Tomcat start automatically, you must create a file in /etc/init.d called tomcat.  Populate the file with the following:
{code}
#!/bin/bash
#
# Startup script for Tomcat server
#
# chkconfig: - 83 53
# description: Starts and stops the Tomcat daemon.
# processname: tomcat
# pidfile: /var/run/tomcat.pid
export JAVA_HOME=/usr/lib/jvm/java-6-sun

# See how we were called.
case $1 in
        start)

su - billservice -c "sh /home/billservice/apache-tomcat-6.0.18/bin/startup.sh"
        ;;
        stop)
su - billservice -c "sh /home/billservice/apache-tomcat-6.0.18/bin/shutdown.sh"
        ;;
        restart)
su - billservice -c "sh /home/billservice/apache-tomcat-6.0.18/bin/shutdown.sh"
su - billservice -c "sh /home/billservice/apache-tomcat-6.0.18/bin/startup.sh"
        ;;
        *)
                echo "Usage: /etc/init.d/tomcat start|stop|restart"
        ;;
esac

exit 0
{code}

</property>
    

<property name="body">First off, do not use Tomcat from the Ubuntu repository - download it yourself, and extract it in the home directory of the user it will run as.  The example given here is from our xmlbill server.

To make Tomcat start automatically, you must create a file in /etc/init.d called tomcat.  Populate the file with the following:
{code}
#!/bin/bash
#
# Startup script for Tomcat server
#
# chkconfig: - 83 53
# description: Starts and stops the Tomcat daemon.
# processname: tomcat
# pidfile: /var/run/tomcat.pid
export JAVA_HOME=/usr/lib/jvm/java-6-sun

# See how we were called.
case $1 in
        start)

su - billservice -c "sh /home/billservice/apache-tomcat-6.0.18/bin/startup.sh"
        ;;
        stop)
su - billservice -c "sh /home/billservice/apache-tomcat-6.0.18/bin/shutdown.sh"
        ;;
        restart)
su - billservice -c "sh /home/billservice/apache-tomcat-6.0.18/bin/shutdown.sh"
su - billservice -c "sh /home/billservice/apache-tomcat-6.0.18/bin/startup.sh"
        ;;
        *)
                echo "Usage: /etc/init.d/tomcat start|stop|restart"
        ;;
esac

exit 0
{code}

A couple of things to note here; we 'su' to the user we want the process to run as.  This is important because we do NOT want processes running as root.  Additionally, we are explicitly setting the JAVA_HOME environment variable here, but you may wish to set it in /etc/profile (system-wide) or ~.bashrc (user-specific).</property>
    

<property name="body">&lt;p&gt;Put the following in the /etc/ntp.conf file:&lt;/p&gt;

&lt;p&gt;restrict default nomodify notrap noquery nopeer kod&lt;br /&gt;
restrict 127.0.0.1&lt;br /&gt;
server time.suu.edu&lt;br /&gt;
server time2.suu.edu&lt;br /&gt;
driftfile /var/lib/ntp/drift&lt;br /&gt;
broadcastdelay&amp;nbsp; 0.008&lt;br class="atl-forced-newline" /&gt;&lt;/p&gt;

&lt;p&gt;Put the following in the /etc/ntp/step-tickers file:\\&lt;/p&gt;

&lt;p&gt;time.suu.edu&lt;br /&gt;
time2.suu.edu&lt;/p&gt;</property>
    

<property name="body">Put the following in the /etc/ntp.conf file:

restrict default nomodify notrap noquery nopeer kod
restrict 127.0.0.1
server time.suu.edu
server time2.suu.edu
driftfile /var/lib/ntp/drift
broadcastdelay&amp;nbsp; 0.008</property>
    

<property name="body">Put the following in the /etc/ntp.conf file:

restrict default nomodify notrap noquery nopeer kod
restrict 127.0.0.1
server time.suu.edu
server time2.suu.edu
driftfile /var/lib/ntp/drift
broadcastdelay&amp;nbsp; 0.008\\

Put the following in the /etc/ntp/step-tickers file:\\

time.suu.edu
time2.suu.edu
127.127.1.0 </property>
    

<property name="body">&lt;p&gt;433179154336b579&lt;/p&gt;</property>
    

<property name="body">h1. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Example contents of dsm.sys file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMmethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu

nodename &lt;servernodename_goeshere&gt; ex. ASPEN
passwordaccess generate
MANAGEDSERVICES	schedule webclient

exclude     /.../core
exclude     /.../tmp/.../*
exclude.dir /proc
exclude.dir /proc/
exclude.dir /dev
exclude.dir /dev/
exclude.dir	/mnt
exclude.dir	/mnt/
exclude.dir /usr/share/man
exclude dsmsched.log
{code}

h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc i
#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Notes

This section added for Ubuntu:For those of you who have seen this before, I've corrected a couple of
errors in it.

I recently built up a linux box using Ubuntu and discovered that it's
not hard to set it up to use the TSM backup client.  Assuming you have
a passing familiarity with setting up TSM on RPM-based distributions,
here are the basic steps:

1. Install the "alien" package which lets you (among other things)
install RPM packages on Ubuntu or other Debian-based distros.

$ sudo apt-get install alien

2.  download the TSM client software from IBM using your web browser.

3.  untar the TSM RPMs...

4.  Use alien to install the appropriate RPMs.

$ sudo alien \-i \--scripts TIVsm-API.i386.rpm TIVsm-BA.i386.rpm

5.  Set up the normal TSM configuration (dsm.opt, dsm.sys, inclexcl.dsm).

6.  Run a manual backup.

$ sudo dsmc incremental

Remember to automate startup via a script in the /etc/init.d directory</property>
    

<property name="body">{code}
The key to creating self-signing certificates in Tomcat is to remember the key files/components involved:
&lt;yourkeystore&gt; and cacerts, and an existing Java HOME variable.


&lt;yourkeystore&gt; will be whatever you decide to call it when creating the self-signed certificate.  For example, the following
command creates a keystore called mykeystore with an alias of tomcat and a validity of 10 years in the C:\ssl directory:

%JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA -keystore C:\ssl\mykeystore -validity 3650
remember first and last name must be the host+domain, i.e. tntrans.suu.edu

Export it:
%JAVA_HOME%\bin\keytool -export -alias tomcat -file D:\ssl\exported.cert -keystore C:\ssl\mykeystore

Once created, then you must import it into your existing CACERTS file for it to be 'trusted':

%JAVA_HOME%\bin\keytool -import -alias tomcat -trustcacerts -file D:\SSL\exported.cert -keystore %JAVA_HOME%\jre\lib\security\cacerts (this pass will be changeit)
{code}</property>
    

<property name="body">&lt;p&gt;Command to remove iptables from Red Hat linux boxes:
&lt;br class="atl-forced-newline" /&gt;&lt;/p&gt;

&lt;p&gt;&amp;nbsp;rpm -e iptables iptables-ipv6 iptstate system-config-securitylevel system-config-securitylevel-tui firstboot system-config-keyboard firstboot-tui system-config-boot libvirt libvirt-python rhn-virtualization-host&lt;/p&gt;</property>
    

<property name="body">{code}
The key to creating self-signing certificates in Tomcat is to remember the key files/components involved:
&lt;yourkeystore&gt; and cacerts, and an existing Java HOME variable.


&lt;yourkeystore&gt; will be whatever you decide to call it when creating the self-signed certificate.  For example, the following
command creates a keystore called mykeystore with an alias of tomcat and a validity of 10 years in the C:\ssl directory:

%JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA -keystore C:\ssl\mykeystore -validity 3650
remember first and last name must be the host+domain, i.e. tntrans.suu.edu

Export it:
%JAVA_HOME%\bin\keytool -export -alias tomcat -file D:\ssl\exported.cert -keystore C:\ssl\mykeystore

Once created, then you must import it into your existing CACERTS file for it to be 'trusted':

%JAVA_HOME%\bin\keytool -import -alias tomcat -trustcacerts -file D:\SSL\exported.cert -keystore %JAVA_HOME%\jre\lib\security\cacerts (this pass will be changeit)
{code}
On the ipsca website:

{color:#333333}&amp;nbsp;{color}{color:#333333}&amp;nbsp;{color}

| {color:#2c63ca}&amp;nbsp;Certificate installation{color} | \\ |
{color:#333333}Installing your Certificate with Jakarta-Tomcat.{color}
{color:#333333}(For Linux &amp; Windows){color}{color:#333333}&amp;nbsp;{color}

| {color:#333333}This document explains how to generate and install a Server Digital Certificate, and answers any question you might have.{color} || {color:#333333}{*}Creating a Certificate Signing Request{*}{color}\\
 | {color:#333333}Follow these instructions to generate a CSR for your Web site. When you have completed this process, you will have a CSR ready to submit to{color}{color:#333333}&amp;nbsp;{color}ipsCA{color:#333333}&amp;nbsp;{color}{color:#333333}in order to be generated into a SSL Security Certificate.{color}\\
{color:#333333}If you are not using JDK 1.4 or higher, you must download and install "Java Secure Socket Extensions" JSSE.{color}\\
{color:#333333}1. Generate a private key with the following command:{color}\\
{color:#333333}$JAVA_HOME/bin/keytool \-genkey \-alias tomcat \-keyalg RSA \-keystore /path/to/domainname.kdb{color}\\
{color:#333333}You will be prompted for a password. Tomcat uses a default password of "changeit". If you use a different password, you will need to specify a custom password in the server.xml configuration file.{color}\\
{color:#333333}In the next field you will be asked "What is your first and last name?" At this prompt, you must specify the common name (FQDN) of your web site.{color}\\
{color:#333333}You will then be prompted for your organizational unit, organization, etc.{color}\\
{color:#333333}.2. Generate the Certificate Signing Request (CSR){color}\\
{color:#333333}$JAVA_HOME/bin/keytool \-certreq \-alias tomcat \-keystore /path/to/keystore.kdb \-file filename.csr{color}\\
{color:#333333}You will not be prompted for the common name, organization, etc. The keytool will use the values that you specify when generating the private key.{color}\\
{color:#333333}3. Now go to{color}{color:#333333}&amp;nbsp;{color}ipsCA{color:#333333}&amp;nbsp;{color}{color:#333333}, select your certificate and fill in the form with your personal data, paste your certificate request in the CSR field and make sure that you include \-----BEGIN NEW CERTIFICATE REQUEST----\- and \-----END NEW CERTIFICATE REQUEST-----.{color}\\
{color:#333333}4. Make a backup of the keystore.kdb key database. It would be useful for you if your server crashes.{color}\\ | |
| {color:#333333}{*}Installing a Server Digital Certificate{*}{color}\\
 | {color:#333333}{*}Upload a New SSL Certificate{*}{color}\\
{color:#333333}After you receive your certificate,{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}two other certificates will be necessary to setup your SSL Server, IPS SERVIDORES ROOT CERTIFICATE and the intermediate CA IPSCA CLASEA1{*}{color}{color:#333333}.{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}It is essential that these certificates are also&amp;nbsp; installed on your webserver in order to establish correct SSL connections{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}with your customer's browsers. Should they be required, you may download these certificates individually or collectively as a bundled file below:{color}\\
IPSServidores.crt\\
IPSCACLASEA1.crt\\
IPS-IPSCABUNDLE.CRT\\
{color:#333333}You must first export the certificates in the following format:{color}
# {color:#333333}Copy the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{_}IPSCACLASEA1 Chained CA certificate{_}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}into a text editor such as notepad and save as{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{_}chain.cer{_}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}on a Windows machine with IE 5+.{color}
# {color:#333333}Copy your{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{_}web server certificate{_}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}into a text editor such as notepad and save as{color}{color:#333333}{_}yourdomain.cer{_}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}on a Windows machine with IE 5+.{color}
# {color:#333333}Copy the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{_}IPSServidores root CA{_}{color}{color:#333333}_&amp;nbsp;_{color}{color:#333333}{_}certificate{_}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}into a text editor and save as{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{_}root.cer{_}{color}{color:#333333}_&amp;nbsp;_{color}{color:#333333}on a Windows machine with IE 5+.{color}
# {color:#333333}Double-click the root.cer and select the Details tab, then Copy to File, then select the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}Base-64{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}option, give your copied certificate a file name of{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}root_der.cer{*}{color}
# {color:#333333}Double-click the chain.cer and select Install. Choose "Place all certificates in following store" and select Intermediate Certification Authorities. Complete the Wizard.{color}
# {color:#333333}Double-click the chain.cer again and select the Details tab, then Copy to File, then select the{color}{color:#333333}{*}Base-64{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}option, give your copied certificate a file name of{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}chain_der.cer{*}{color}
# {color:#333333}Double click the youdomain.cer and select the Details tab, then Copy to File, then select the{color}{color:#333333}{*}PKCS#7 (p7b)*{color}{color:#333333}&amp;nbsp;{color}{color:#333333}option, also select the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}Include all certificates in the certification path{*}{color}{color:#333333}, give your copied certificate a file name of{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}yourdomain.p7b{*}{color}{color:#333333}{*}The following certificate installations must be executed in the stated order.*{color}\\
{color:#333333}1. Import the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}root_der.cer{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}and{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}chain_der.cer{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}files using:{color}{color:#333333}*$ keytool \-import \-trustcacerts \-keystore my.kdb \-alias root - file root_der.cer{*}{color}\\
{color:#333333}*$ keytool \-import \-trustcacerts \-keystore my.kdb \-alias chain - file chain_der.cer{*}{color}{color:#333333}With my.kdb being your keystore.{color}\\
{color:#333333}2. Import the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}yourdomain.p7b file{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}using:{color}{color:#333333}{*}keytool \-import \-trustcacerts \-keystore my.kdb \-alias tomcat \-file yourdomain.p7b{*}{color}{color:#333333}With my.kdb being your keystore.{color}\\
{color:#333333}&amp;nbsp;{color}\\
{color:#333333}{*}Update server.xml configuration file:*{color}\\
{color:#333333}1. Open "$JAKARTA_HOME/conf/server.xml" in a text editor.{color}\\
{color:#333333}2. Find the following section:{color}\\
{color:#333333}&lt;Connector{color}{color:#333333}&amp;nbsp;{color}\\
 {color:#333333}...{color}{color:#333333}&amp;nbsp;{color}\\
 {color:#333333}scheme="https"{color}{color:#333333}&amp;nbsp;{color}\\
 {color:#333333}secure="true"{color}{color:#333333}&amp;nbsp;{color}\\
 {color:#333333}keystoreFile="/pathto/my.kdb"{color}{color:#333333}&amp;nbsp;{color}\\
 {color:#333333}keystorePass="mypassword"{color}\\
{color:#333333}3. If you want Tomcat to use the default SSL port, change all instances of the port number 8443 to 443.{color}\\
{color:#333333}4. Add the keystoreFile and keystorePass directives to correspond with the keystore file and password that you are using.{color}\\
{color:#333333}5. Start or restart Tomcat using the appropriate startup script (startup.sh for unix/linux or startup.bat for windows){color} | |</property>
    

<property name="body">h1. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Example contents of dsm.sys file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMmethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu

nodename &lt;servernodename_goeshere&gt; ex. ASPEN
passwordaccess generate
MANAGEDSERVICES	schedule webclient

exclude core
exclude /.../core
exclude /.../tmp/.../*
exclude *_log
exclude *.log
exclude /tmp/*/.../*
exclude /mnt/*/.../*
exclude /.../Cache/*/.../*
exclude /var/run/*/.../*
exclude /var/tmp/*/.../*
exclude /proc/*/.../*
exclude /u0?/oradata/*/.../*
exclude /backup/*/.../*
exclude.dir /proc
exclude.dir /proc/
exclude.dir /dev
exclude.dir /dev/
exclude.dir /mnt
exclude.dir /mnt/
exclude.dir /usr/share/man
exclude dsmsched.log
exclude.dir /var/spool/cups/
exclude.dir /u01/app/sct/suupics
exclude.dir /u01/app/sct/suupics-www
exclude /u01/app/sct/suupics/*
exclude /u01/app/sct/suupics-www/*
{code}

h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc i
#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Notes

This section added for Ubuntu:For those of you who have seen this before, I've corrected a couple of
errors in it.

I recently built up a linux box using Ubuntu and discovered that it's
not hard to set it up to use the TSM backup client.  Assuming you have
a passing familiarity with setting up TSM on RPM-based distributions,
here are the basic steps:

1. Install the "alien" package which lets you (among other things)
install RPM packages on Ubuntu or other Debian-based distros.

$ sudo apt-get install alien

2.  download the TSM client software from IBM using your web browser.

3.  untar the TSM RPMs...

4.  Use alien to install the appropriate RPMs.

$ sudo alien \-i \--scripts TIVsm-API.i386.rpm TIVsm-BA.i386.rpm

5.  Set up the normal TSM configuration (dsm.opt, dsm.sys, inclexcl.dsm).

6.  Run a manual backup.

$ sudo dsmc incremental

Remember to automate startup via a script in the /etc/init.d directory</property>
    

<property name="body">h1. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Example contents of dsm.sys file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMmethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu

nodename &lt;servernodename_goeshere&gt; ex. ASPEN
passwordaccess generate
MANAGEDSERVICES	schedule webclient

exclude core
exclude /.../core
exclude /.../tmp/.../*
exclude *_log
exclude *.log
exclude /tmp/*/.../*
exclude /mnt/*/.../*
exclude /.../Cache/*/.../*
exclude /var/run/*/.../*
exclude /var/tmp/*/.../*
exclude /proc/*/.../*
exclude /u0?/oradata/*/.../*
exclude /backup/*/.../*
exclude.dir /proc
exclude.dir /proc/
exclude.dir /dev
exclude.dir /dev/
exclude.dir /mnt
exclude.dir /mnt/
exclude.dir /usr/share/man
exclude dsmsched.log
exclude.dir /var/spool/cups/
exclude.dir /u01/app/sct/suupics
exclude.dir /u01/app/sct/suupics-www
exclude /u01/app/sct/suupics/*
exclude /u01/app/sct/suupics-www/*
{code}

h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc
It will prompt you for your nodename and password.  Once you have entered them, it will drop you at a tsm&gt; prompt.  You can then type 'backup', no quotes, and it will start an incremental backup.  If you don't want to start one right away, just type 'quit', no quotes, and it will drop you back at the linux prompt.
To start the daemon, run the following command:

#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Notes

This section added for Ubuntu:For those of you who have seen this before, I've corrected a couple of
errors in it.

I recently built up a linux box using Ubuntu and discovered that it's
not hard to set it up to use the TSM backup client.  Assuming you have
a passing familiarity with setting up TSM on RPM-based distributions,
here are the basic steps:

1. Install the "alien" package which lets you (among other things)
install RPM packages on Ubuntu or other Debian-based distros.

$ sudo apt-get install alien

2.  download the TSM client software from IBM using your web browser.

3.  untar the TSM RPMs...

4.  Use alien to install the appropriate RPMs.

$ sudo alien \-i \--scripts TIVsm-API.i386.rpm TIVsm-BA.i386.rpm

5.  Set up the normal TSM configuration (dsm.opt, dsm.sys, inclexcl.dsm).

6.  Run a manual backup.

$ sudo dsmc incremental

Remember to automate startup via a script in the /etc/init.d directory</property>
    

<property name="body">{code}
The key to creating self-signing certificates in Tomcat is to remember the key files/components involved:
&lt;yourkeystore&gt; and cacerts, and an existing Java HOME variable.


&lt;yourkeystore&gt; will be whatever you decide to call it when creating the self-signed certificate.  For example, the following
command creates a keystore called mykeystore with an alias of tomcat and a validity of 10 years in the C:\ssl directory:

%JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA -keystore C:\ssl\mykeystore -validity 3650
remember first and last name must be the host+domain, i.e. tntrans.suu.edu

Export it:
%JAVA_HOME%\bin\keytool -export -alias tomcat -file D:\ssl\exported.cert -keystore C:\ssl\mykeystore

Once created, then you must import it into your existing CACERTS file for it to be 'trusted':

%JAVA_HOME%\bin\keytool -import -alias tomcat -trustcacerts -file D:\SSL\exported.cert -keystore %JAVA_HOME%\jre\lib\security\cacerts (this pass will be changeit)
{code}
On the ipsca website:

{color:#333333}&amp;nbsp;{color}{color:#333333}&amp;nbsp;{color}
| {color:#2c63ca}&amp;nbsp;Certificate installation{color} | \\ |
{color:#333333}Installing your Certificate with Jakarta-Tomcat.{color}
{color:#333333}(For Linux &amp; Windows){color}{color:#333333}&amp;nbsp;{color}
| {color:#333333}This document explains how to generate and install a Server Digital Certificate, and answers any question you might have.{color} || {color:#333333}{*}Creating a Certificate Signing Request{*}{color}\\ |
| {color:#333333}Follow these instructions to generate a CSR for your Web site. When you have completed this process, you will have a CSR ready to submit to{color}{color:#333333}&amp;nbsp;{color}ipsCA{color:#333333}&amp;nbsp;{color}{color:#333333}in order to be generated into a SSL Security Certificate.{color}\\ {color:#333333}If you are not using JDK 1.4 or higher, you must download and install "Java Secure Socket Extensions" JSSE.{color}\\ {color:#333333}1. Generate a private key with the following command:{color}\\ {color:#333333}$JAVA_HOME/bin/keytool \-genkey \-alias tomcat \-keyalg RSA \-keystore /path/to/domainname.kdb{color}\\ {color:#333333}You will be prompted for a password. Tomcat uses a default password of "changeit". If you use a different password, you will need to specify a custom password in the server.xml configuration file.{color}\\ {color:#333333}In the next field you will be asked "What is your first and last name?" At this prompt, you must specify the common name (FQDN) of your web site.{color}\\ {color:#333333}You will then be prompted for your organizational unit, organization, etc.{color}\\ {color:#333333}.2. Generate the Certificate Signing Request (CSR){color}\\ {color:#333333}$JAVA_HOME/bin/keytool \-certreq \-alias tomcat \-keystore /path/to/keystore.kdb \-file filename.csr{color}\\ {color:#333333}You will not be prompted for the common name, organization, etc. The keytool will use the values that you specify when generating the private key.{color}\\ {color:#333333}3. Now go to{color}{color:#333333}&amp;nbsp;{color}ipsCA{color:#333333}&amp;nbsp;{color}{color:#333333}, select your certificate and fill in the form with your personal data, paste your certificate request in the CSR field and make sure that you include \---\-{color}{color:#333333}{-}BEGIN NEW CERTIFICATE REQUEST{-}{color}{color:#333333}\-\-{color}{color:#333333}-\- and --{color}{color:#333333}\-\-{color}{color:#333333}{-}END NEW CERTIFICATE REQUEST{-}{color}{color:#333333}\----.{color}\\ {color:#333333}4. Make a backup of the keystore.kdb key database. It would be useful for you if your server crashes.{color}\\ | |
| {color:#333333}{*}Installing a Server Digital Certificate{*}{color}\\ |
| {color:#333333}{*}Upload a New SSL Certificate{*}{color}\\ {color:#333333}After you receive your certificate,{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}two other certificates will be necessary to setup your SSL Server, IPS SERVIDORES ROOT CERTIFICATE and the intermediate CA IPSCA CLASEA1{*}{color}{color:#333333}.{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}It is essential that these certificates are also&amp;nbsp; installed on your webserver in order to establish correct SSL connections{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}with your customer's browsers. Should they be required, you may download these certificates individually or collectively as a bundled file below:{color}\\
IPSServidores.crt \\
IPSCACLASEA1.crt \\
IPS-IPSCABUNDLE.CRT \\ {color:#333333}You must first export the certificates in the following format:{color}
# {color:#333333}Copy the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{_}IPSCACLASEA1 Chained CA certificate{_}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}into a text editor such as notepad and save as{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{_}chain.cer{_}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}on a Windows machine with IE 5+.{color}
# {color:#333333}Copy your{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{_}web server certificate{_}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}into a text editor such as notepad and save as{color}{color:#333333}{_}yourdomain.cer{_}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}on a Windows machine with IE 5+.{color}
# {color:#333333}Copy the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{_}IPSServidores root CA{_}{color}{color:#333333}_&amp;nbsp;_{color}{color:#333333}{_}certificate{_}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}into a text editor and save as{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{_}root.cer{_}{color}{color:#333333}_&amp;nbsp;_{color}{color:#333333}on a Windows machine with IE 5+.{color}
# {color:#333333}Double-click the root.cer and select the Details tab, then Copy to File, then select the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}Base-64{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}option, give your copied certificate a file name of{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}root_der.cer{*}{color}
# {color:#333333}Double-click the chain.cer and select Install. Choose "Place all certificates in following store" and select Intermediate Certification Authorities. Complete the Wizard.{color}
# {color:#333333}Double-click the chain.cer again and select the Details tab, then Copy to File, then select the{color}{color:#333333}{*}Base-64{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}option, give your copied certificate a file name of{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}chain_der.cer{*}{color}
# {color:#333333}Double click the youdomain.cer and select the Details tab, then Copy to File, then select the{color}{color:#333333}{*}PKCS#7 (p7b)*{color}{color:#333333}&amp;nbsp;{color}{color:#333333}option, also select the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}Include all certificates in the certification path{*}{color}{color:#333333}, give your copied certificate a file name of{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}yourdomain.p7b{*}{color}{color:#333333}{*}The following certificate installations must be executed in the stated order.*{color}\\ {color:#333333}1. Import the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}root_der.cer{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}and{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}chain_der.cer{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}files using:{color}{color:#333333}*$ keytool \-import \-trustcacerts \-keystore my.kdb \-alias root - file root_der.cer{*}{color}\\ {color:#333333}*$ keytool \-import \-trustcacerts \-keystore my.kdb \-alias chain - file chain_der.cer{*}{color}{color:#333333}With my.kdb being your keystore.{color}\\ {color:#333333}2. Import the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}yourdomain.p7b file{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}using:{color}{color:#333333}{*}keytool \-import \-trustcacerts \-keystore my.kdb \-alias tomcat \-file yourdomain.p7b{*}{color}{color:#333333}With my.kdb being your keystore.{color}\\ {color:#333333}&amp;nbsp;{color}\\ {color:#333333}{*}Update server.xml configuration{color} {color:#333333}[file:*]{color}\\ {color:#333333}1. Open "$JAKARTA_HOME/conf/server.xml" in a text editor.{color}\\ {color:#333333}2. Find the following section:{color}\\ {color:#333333}&lt;Connector{color}{color:#333333}&amp;nbsp;{color}\\ {color:#333333}...{color}{color:#333333}&amp;nbsp;{color}\\ {color:#333333}scheme="https"{color}{color:#333333}&amp;nbsp;{color}\\ {color:#333333}secure="true"{color}{color:#333333}&amp;nbsp;{color}\\ {color:#333333}keystoreFile="/pathto/my.kdb"{color}{color:#333333}&amp;nbsp;{color}\\ {color:#333333}keystorePass="mypassword"{color}\\ {color:#333333}3. If you want Tomcat to use the default SSL port, change all instances of the port number 8443 to 443.{color}\\ {color:#333333}4. Add the keystoreFile and keystorePass directives to correspond with the keystore file and password that you are using.{color}\\ {color:#333333}5. Start or restart Tomcat using the appropriate startup script (startup.sh for unix/linux or startup.bat for windows){color} | |</property>
    

<property name="body">{code}
The key to creating self-signing certificates in Tomcat is to remember the key files/components involved:
&lt;yourkeystore&gt; and cacerts, and an existing Java HOME variable.


&lt;yourkeystore&gt; will be whatever you decide to call it when creating the self-signed certificate.  For example, the following
command creates a keystore called mykeystore with an alias of tomcat and a validity of 10 years in the C:\ssl directory:

%JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA -keystore C:\ssl\mykeystore -validity 3650
remember first and last name must be the host+domain, i.e. tntrans.suu.edu

Export it:
%JAVA_HOME%\bin\keytool -export -alias tomcat -file D:\ssl\exported.cert -keystore C:\ssl\mykeystore

Once created, then you must import it into your existing CACERTS file for it to be 'trusted':

%JAVA_HOME%\bin\keytool -import -alias tomcat -trustcacerts -file D:\SSL\exported.cert -keystore %JAVA_HOME%\jre\lib\security\cacerts (this pass will be changeit)
{code}
On the ipsca website:

{color:#333333}&amp;nbsp;{color}{color:#333333}&amp;nbsp;{color}
| {color:#2c63ca}&amp;nbsp;Certificate installation{color} | \\ |
{color:#333333}Installing your Certificate with Jakarta-Tomcat.{color}
{color:#333333}(For Linux &amp; Windows){color}{color:#333333}&amp;nbsp;{color}
| {color:#333333}This document explains how to generate and install a Server Digital Certificate, and answers any question you might have.{color} || {color:#333333}{*}Creating a Certificate Signing Request{*}{color}\\ |
| {color:#333333}Follow these instructions to generate a CSR for your Web site. When you have completed this process, you will have a CSR ready to submit to{color}{color:#333333}&amp;nbsp;{color}ipsCA{color:#333333}&amp;nbsp;{color}{color:#333333}in order to be generated into a SSL Security Certificate.{color}\\ {color:#333333}If you are not using JDK 1.4 or higher, you must download and install "Java Secure Socket Extensions" JSSE.{color}\\ {color:#333333}1. Generate a private key with the following command:{color}\\ {color:#333333}*$JAVA_HOME/bin/keytool \-genkey \-alias tomcat \-keyalg RSA \-keystore /path/to/domainname.kdb*{color}\\ {color:#333333}You will be prompted for a password. Tomcat uses a default password of "changeit". If you use a different password, you will need to specify a custom password in the server.xml configuration file.{color}\\ {color:#333333}In the next field you will be asked "What is your first and last name?" At this prompt, you must specify the common name (FQDN) of your web site.{color}\\ {color:#333333}You will then be prompted for your organizational unit, organization, etc.{color}\\ {color:#333333}.2. Generate the Certificate Signing Request (CSR){color}\\ {color:#333333}$JAVA_HOME/bin/keytool \-certreq \-alias tomcat \-keystore /path/to/keystore.kdb \-file filename.csr{color}\\ {color:#333333}You will not be prompted for the common name, organization, etc. The keytool will use the values that you specify when generating the private key.{color}\\ {color:#333333}3. Now go to{color}{color:#333333}&amp;nbsp;{color}ipsCA{color:#333333}&amp;nbsp;{color}{color:#333333}, select your certificate and fill in the form with your personal data, paste your certificate request in the CSR field and make sure that you include \---\-{color}{color:#333333}{-}BEGIN NEW CERTIFICATE REQUEST{-}{color}{color:#333333}\-\-{color}{color:#333333}-\- and --{color}{color:#333333}\-\-{color}{color:#333333}{-}END NEW CERTIFICATE REQUEST{-}{color}{color:#333333}\----.{color}\\ {color:#333333}4. Make a backup of the keystore.kdb key database. It would be useful for you if your server crashes.{color}\\ | |
| {color:#333333}{*}Installing a Server Digital Certificate{*}{color}\\ |
| {color:#333333}{*}Upload a New SSL Certificate{*}{color}\\ {color:#333333}After you receive your certificate,{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}two other certificates will be necessary to setup your SSL Server, IPS SERVIDORES ROOT CERTIFICATE and the intermediate CA IPSCA CLASEA1{*}{color}{color:#333333}.{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}It is essential that these certificates are also&amp;nbsp; installed on your webserver in order to establish correct SSL connections{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}with your customer's browsers. Should they be required, you may download these certificates individually or collectively as a bundled file below:{color}\\
IPSServidores.crt \\
IPSCACLASEA1.crt \\
IPS-IPSCABUNDLE.CRT \\ {color:#333333}You must first export the certificates in the following format:{color}
# {color:#333333}Copy the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{_}IPSCACLASEA1 Chained CA certificate{_}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}into a text editor such as notepad and save as{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{_}chain.cer{_}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}on a Windows machine with IE 5+.{color}
# {color:#333333}Copy your{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{_}web server certificate{_}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}into a text editor such as notepad and save as{color}{color:#333333}{_}yourdomain.cer{_}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}on a Windows machine with IE 5+.{color}
# {color:#333333}Copy the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{_}IPSServidores root CA{_}{color}{color:#333333}_&amp;nbsp;_{color}{color:#333333}{_}certificate{_}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}into a text editor and save as{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{_}root.cer{_}{color}{color:#333333}_&amp;nbsp;_{color}{color:#333333}on a Windows machine with IE 5+.{color}
# {color:#333333}Double-click the root.cer and select the Details tab, then Copy to File, then select the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}Base-64{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}option, give your copied certificate a file name of{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}root_der.cer{*}{color}
# {color:#333333}Double-click the chain.cer and select Install. Choose "Place all certificates in following store" and select Intermediate Certification Authorities. Complete the Wizard.{color}
# {color:#333333}Double-click the chain.cer again and select the Details tab, then Copy to File, then select the{color}{color:#333333}{*}Base-64{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}option, give your copied certificate a file name of{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}chain_der.cer{*}{color}
# {color:#333333}Double click the youdomain.cer and select the Details tab, then Copy to File, then select the{color}{color:#333333}{*}PKCS#7 (p7b)*{color}{color:#333333}&amp;nbsp;{color}{color:#333333}option, also select the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}Include all certificates in the certification path{*}{color}{color:#333333}, give your copied certificate a file name of{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}yourdomain.p7b{*}{color}{color:#333333}{*}The following certificate installations must be executed in the stated order.*{color}\\ {color:#333333}1. Import the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}root_der.cer{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}and{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}chain_der.cer{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}files using:{color}{color:#333333}*$ keytool \-import \-trustcacerts \-keystore my.kdb \-alias root - file root_der.cer{*}{color}\\ {color:#333333}*$ keytool \-import \-trustcacerts \-keystore my.kdb \-alias chain - file chain_der.cer{*}{color}{color:#333333}With my.kdb being your keystore.{color}\\ {color:#333333}2. Import the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}yourdomain.p7b file{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}using:{color}{color:#333333}{*}keytool \-import \-trustcacerts \-keystore my.kdb \-alias tomcat \-file yourdomain.p7b{*}{color}{color:#333333}With my.kdb being your keystore.{color}\\ {color:#333333}&amp;nbsp;{color}\\ {color:#333333}{*}Update server.xml configuration{color} {color:#333333}[file:*]{color}\\ {color:#333333}1. Open "$JAKARTA_HOME/conf/server.xml" in a text editor.{color}\\ {color:#333333}2. Find the following section:{color}\\ {color:#333333}&lt;Connector{color}{color:#333333}&amp;nbsp;{color}\\ {color:#333333}...{color}{color:#333333}&amp;nbsp;{color}\\ {color:#333333}scheme="https"{color}{color:#333333}&amp;nbsp;{color}\\ {color:#333333}secure="true"{color}{color:#333333}&amp;nbsp;{color}\\ {color:#333333}keystoreFile="/pathto/my.kdb"{color}{color:#333333}&amp;nbsp;{color}\\ {color:#333333}keystorePass="mypassword"{color}\\ {color:#333333}3. If you want Tomcat to use the default SSL port, change all instances of the port number 8443 to 443.{color}\\ {color:#333333}4. Add the keystoreFile and keystorePass directives to correspond with the keystore file and password that you are using.{color}\\ {color:#333333}5. Start or restart Tomcat using the appropriate startup script (startup.sh for unix/linux or startup.bat for windows){color} | |</property>
    

<property name="body">Command to remove iptables from Red Hat linux boxes:
\\

&amp;nbsp;rpm \-e iptables iptables-ipv6 iptstate system-config-securitylevel system-config-securitylevel-tui firstboot system-config-keyboard firstboot-tui </property>
    

<property name="body">First off, do not use Tomcat from the Ubuntu repository - download it yourself, and extract it in the home directory of the user it will run as.  The example given here is from our xmlbill server.

h5. Step 1: To make Tomcat start automatically, you must create a file in /etc/init.d called tomcat.  Populate the file with the following:
{code}
#!/bin/bash
#
# Startup script for Tomcat server
#
# chkconfig: - 83 53
# description: Starts and stops the Tomcat daemon.
# processname: tomcat
# pidfile: /var/run/tomcat.pid
export JAVA_HOME=/usr/lib/jvm/java-6-sun

# See how we were called.
case $1 in
        start)

su - billservice -c "sh /home/billservice/apache-tomcat-6.0.18/bin/startup.sh"
        ;;
        stop)
su - billservice -c "sh /home/billservice/apache-tomcat-6.0.18/bin/shutdown.sh"
        ;;
        restart)
su - billservice -c "sh /home/billservice/apache-tomcat-6.0.18/bin/shutdown.sh"
su - billservice -c "sh /home/billservice/apache-tomcat-6.0.18/bin/startup.sh"
        ;;
        *)
                echo "Usage: /etc/init.d/tomcat start|stop|restart"
        ;;
esac

exit 0
{code}

A couple of things to note here; we 'su' to the user we want the process to run as.  This is important because we do NOT want processes running as root.  Additionally, we are explicitly setting the JAVA_HOME environment variable here, but you may wish to set it in /etc/profile (system-wide) or ~.bashrc (user-specific).

h5. Set to start automatically
Run the following commands as root:
{code}
#chmod 755 /etc/init.d/tomcat
#update-rc.d tomcat defaults
{code}
That's it; reboot to verify that everything starts the way you expect.</property>
    

<property name="body">&lt;ac:macro ac:name="suu-info"&gt;&lt;ac:rich-text-body&gt;
&lt;p&gt;A place to collect Tomcat documentation.&lt;/p&gt;&lt;/ac:rich-text-body&gt;&lt;/ac:macro&gt;

&lt;h2&gt;Tomcat Documentation&lt;/h2&gt;

&lt;ac:macro ac:name="suu-tip"&gt;&lt;ac:rich-text-body&gt;
&lt;p&gt;The following list is a collection of Tomcat documentation from all over our wiki. Anything with the label &amp;quot;tomcat&amp;quot; will show up in this list.&lt;/p&gt;&lt;/ac:rich-text-body&gt;&lt;/ac:macro&gt;

&lt;ac:structured-macro ac:name="contentbylabel" ac:schema-version="3" ac:macro-id="a3fd06db-7e68-401b-932d-bc3d2a0d6a39"&gt;&lt;ac:parameter ac:name="labels"&gt;tomcat&lt;/ac:parameter&gt;&lt;ac:parameter ac:name="cql"&gt;label = &amp;quot;tomcat&amp;quot;&lt;/ac:parameter&gt;&lt;/ac:structured-macro&gt;</property>
    

<property name="body">&lt;p&gt;From Dave Iler:&lt;/p&gt;

&lt;p&gt;This document tells how to switch from sendmail to postfix under Redhat AS 4.&lt;br /&gt;
The info was found with google &amp;amp; applied to ginkgo.&amp;nbsp; It worked.&lt;br /&gt;
1)&amp;nbsp; service sendmail stop&lt;br /&gt;
2)&amp;nbsp;&amp;nbsp;&amp;nbsp; chkconfig sendmail off&lt;br /&gt;
3)&amp;nbsp;&amp;nbsp;&amp;nbsp; alternatives --display mta&lt;br /&gt;
4)&amp;nbsp;&amp;nbsp;&amp;nbsp; alternatives --config mta&lt;br /&gt;
At this point the alteratives program will offer you a menu of choices for&lt;br /&gt;
the mta.&amp;nbsp; The default will have a &lt;ac:emoticon ac:name="plus" /&gt; plus sign by it.&amp;nbsp; Often, sendmail is&lt;br /&gt;
the first choice and has a &lt;ac:emoticon ac:name="plus" /&gt; by it; and postfix is listed second.&lt;br /&gt;
Press the number that refers to postfix &amp;amp; hit the &amp;lt;enter&amp;gt; key.&lt;br /&gt;
5)&amp;nbsp;&amp;nbsp;&amp;nbsp; chkconfig postfix on&lt;br /&gt;
6)&amp;nbsp;&amp;nbsp;&amp;nbsp; service postfix start&lt;br /&gt;
At this point you should be able to enter the next command and see something&lt;br /&gt;
like this:&lt;br /&gt;
[root@ginkgo ~]# alternatives --display mta&lt;br /&gt;
mta - status is manual.&lt;br /&gt;
&amp;nbsp;link currently points to /usr/sbin/sendmail.postfix&lt;br /&gt;
/usr/sbin/sendmail.sendmail - priority 90&lt;br /&gt;
&amp;nbsp;slave mta-pam: /etc/pam.d/smtp.sendmail&lt;br /&gt;
&amp;nbsp;slave mta-mailq: /usr/bin/mailq.sendmail&lt;br /&gt;
&amp;nbsp;slave mta-newaliases: /usr/bin/newaliases.sendmail&lt;br /&gt;
&amp;nbsp;slave mta-rmail: /usr/bin/rmail.sendmail&lt;br /&gt;
&amp;nbsp;slave mta-sendmail: /usr/lib/sendmail.sendmail&lt;br /&gt;
&amp;nbsp;slave mta-mailqman: /usr/share/man/man1/mailq.sendmail.1.gz&lt;br /&gt;
&amp;nbsp;slave mta-newaliasesman: /usr/share/man/man1/newaliases.sendmail.1.gz&lt;br /&gt;
&amp;nbsp;slave mta-aliasesman: /usr/share/man/man5/aliases.sendmail.5.gz&lt;br /&gt;
&amp;nbsp;slave mta-sendmailman: /usr/share/man/man8/sendmail.sendmail.8.gz&lt;br /&gt;
/usr/sbin/sendmail.postfix - priority 30&lt;br /&gt;
&amp;nbsp;slave mta-pam: /etc/pam.d/smtp.postfix&lt;br /&gt;
&amp;nbsp;slave mta-mailq: /usr/bin/mailq.postfix&lt;br /&gt;
&amp;nbsp;slave mta-newaliases: /usr/bin/newaliases.postfix&lt;br /&gt;
&amp;nbsp;slave mta-rmail: /usr/bin/rmail.postfix&lt;br /&gt;
&amp;nbsp;slave mta-sendmail: /usr/lib/sendmail.postfix&lt;br /&gt;
&amp;nbsp;slave mta-mailqman: /usr/share/man/man1/mailq.postfix.1.gz&lt;br /&gt;
&amp;nbsp;slave mta-newaliasesman: /usr/share/man/man1/newaliases.postfix.1.gz&lt;br /&gt;
&amp;nbsp;slave mta-aliasesman: /usr/share/man/man5/aliases.postfix.5.gz&lt;br /&gt;
&amp;nbsp;slave mta-sendmailman: /usr/share/man/man1/sendmail.postfix.1.gz&lt;br /&gt;
Current `best' version is /usr/sbin/sendmail.sendmail.&lt;br /&gt;
Sendmail can now be removed, if desired.&lt;/p&gt;</property>
    

<property name="body">&lt;ac:structured-macro ac:macro-id="46a525b0-4b06-47b6-8d83-7d04a3f50995" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 1.0  (buildd@palmer)  Sun Feb  1 20:21:04 UTC 2009

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "Module"
    Load           "dbe"
    Load           "extmod"
    Load           "type1"
    Load           "freetype"
    Load           "glx"
EndSection

Section "ServerFlags"
    Option         "Xinerama" "0"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "DELL 2407WFP"
    HorizSync       30.0 - 83.0
    VertRefresh     56.0 - 60.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce 9800 GT"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "TwinView" "1"
    Option         "metamodes" "DFP-0: nvidia-auto-select +0+0, DFP-1: 1920x1200_60 +1920+0"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;</property>
    

<property name="body">h1. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Example contents of dsm.sys file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMmethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu

nodename &lt;servernodename_goeshere&gt; ex. ASPEN
passwordaccess generate
MANAGEDSERVICES	schedule webclient

exclude core
exclude /.../core
exclude /.../tmp/.../*
exclude *_log
exclude *.log
exclude /tmp/*/.../*
exclude /mnt/*/.../*
exclude /.../Cache/*/.../*
exclude /var/run/*/.../*
exclude /var/tmp/*/.../*
exclude /proc/*/.../*
exclude /u0?/oradata/*/.../*
exclude /backup/*/.../*
exclude.dir /proc
exclude.dir /proc/
exclude.dir /dev
exclude.dir /dev/
exclude.dir /mnt
exclude.dir /mnt/
exclude.dir /usr/share/man
exclude dsmsched.log
exclude.dir /var/spool/cups/
exclude.dir /u01/app/sct/suupics
exclude.dir /u01/app/sct/suupics-www
exclude /u01/app/sct/suupics/*
exclude /u01/app/sct/suupics-www/*
{code}

h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc
It will prompt you for your nodename and password.  Once you have entered them, it will drop you at a tsm&gt; prompt.
You can then type 'backup', no quotes, and it will start an incremental backup.  If you don't want to start one right away,
just type 'quit', no quotes, and it will drop you back at the linux prompt.
To start the daemon, run the following command:

#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Notes

This section added for Ubuntu:For those of you who have seen this before, I've corrected a couple of
errors in it.

I recently built up a linux box using Ubuntu and discovered that it's
not hard to set it up to use the TSM backup client.  Assuming you have
a passing familiarity with setting up TSM on RPM-based distributions,
here are the basic steps:

1. Install the "alien" package which lets you (among other things)
install RPM packages on Ubuntu or other Debian-based distros.

$ sudo apt-get install alien

2.  download the TSM client software from IBM using your web browser.

3.  untar the TSM RPMs...

4.  Use alien to install the appropriate RPMs.

$ sudo alien \-i \--scripts TIVsm-API.i386.rpm TIVsm-BA.i386.rpm

5.  Set up the normal TSM configuration (dsm.opt, dsm.sys, inclexcl.dsm).

6.  Run a manual backup.

$ sudo dsmc incremental

Remember to automate startup via a script in the /etc/init.d directory</property>
    

<property name="body">h1. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}
h2. Example contents of dsm.sys file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMmethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu

nodename &lt;servernodename_goeshere&gt; ex. ASPEN
passwordaccess generate
MANAGEDSERVICES	schedule webclient

exclude core
exclude /.../core
exclude /.../tmp/.../*
exclude *_log
exclude *.log
exclude /tmp/*/.../*
exclude /mnt/*/.../*
exclude /.../Cache/*/.../*
exclude /var/run/*/.../*
exclude /var/tmp/*/.../*
exclude /proc/*/.../*
exclude /u0?/oradata/*/.../*
exclude /backup/*/.../*
exclude.dir /proc
exclude.dir /proc/
exclude.dir /dev
exclude.dir /dev/
exclude.dir /mnt
exclude.dir /mnt/
exclude.dir /usr/share/man
exclude dsmsched.log
exclude.dir /var/spool/cups/
exclude.dir /u01/app/sct/suupics
exclude.dir /u01/app/sct/suupics-www
exclude /u01/app/sct/suupics/*
exclude /u01/app/sct/suupics-www/*
{code}
h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}
h4. Next, execute the following commands:

{code}
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}
h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc
It will prompt you for your nodename and password.  Once you have entered them, it will drop you at a tsm&gt; prompt.
You can then type 'backup', no quotes, and it will start an incremental backup.  If you don't want to start one right away,
just type 'quit', no quotes, and it will drop you back at the linux prompt.
To start the daemon, run the following command:

#/etc/init.d/suu_tivoli start
{code}
h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}
h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}
h2. Ubuntu Notes

This section added for Ubuntu:For those of you who have seen this before, I've corrected a couple of
errors in it.

I recently built up a linux box using Ubuntu and discovered that it's
not hard to set it up to use the TSM backup client.  Assuming you have
a passing familiarity with setting up TSM on RPM-based distributions,
here are the basic steps:

1. Install the "alien" package which lets you (among other things)
install RPM packages on Ubuntu or other Debian-based distros.&amp;nbsp; For 64-bit, you'll also need the ia32-libs package set.


$ sudo apt-get install alien

$ sudo apt-get install ia32-libs (for 64-bit only)


2.  download the TSM client software from IBM using your web browser.

3.  untar the TSM RPMs...

4.  Use alien to install the appropriate RPMs.

$ sudo alien \-i \--scripts TIVsm-API.i386.rpm TIVsm-BA.i386.rpm

5.  Set up the normal TSM configuration (dsm.opt, dsm.sys, inclexcl.dsm).

6.  Run a manual backup.

$ sudo dsmc incremental

Remember to automate startup via a script in the /etc/init.d directory</property>
    

<property name="body">h1. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Example contents of dsm.sys file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMmethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu

nodename &lt;servernodename_goeshere&gt; ex. ASPEN
passwordaccess generate
MANAGEDSERVICES	schedule webclient

exclude core
exclude /.../core
exclude /.../tmp/.../*
exclude *_log
exclude *.log
exclude /tmp/*/.../*
exclude /mnt/*/.../*
exclude /.../Cache/*/.../*
exclude /var/run/*/.../*
exclude /var/tmp/*/.../*
exclude /proc/*/.../*
exclude /u0?/oradata/*/.../*
exclude /backup/*/.../*
exclude.dir /proc
exclude.dir /proc/
exclude.dir /dev
exclude.dir /dev/
exclude.dir /mnt
exclude.dir /mnt/
exclude.dir /usr/share/man
exclude dsmsched.log
exclude.dir /var/spool/cups/
exclude.dir /u01/app/sct/suupics
exclude.dir /u01/app/sct/suupics-www
exclude /u01/app/sct/suupics/*
exclude /u01/app/sct/suupics-www/*
{code}

h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc
It will prompt you for your nodename and password.  Once you have entered them, it will drop you at a tsm&gt; prompt.
You can then type 'backup', no quotes, and it will start an incremental backup.  If you don't want to start one right away,
just type 'quit', no quotes, and it will drop you back at the linux prompt.
To start the daemon, run the following command:

#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Server Notes

Installing TSM Client V5.5.1 on Ubuntu 9.04/amd64
Note: These instructions are based on the report "TSM-Client unter Debian/etch einrichten" at "https://wiki.gw.dg.de/index.php/TSM:debian"
1)  get the RPMs
wget "ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v5r5/Linux/LinuxX86/v551/5.5.1.0-TIV-TSMBAC-LinuxX86.tar"
2)  additional software that may be required (not sure if this is really required, but it works when these are installed)
apt-get install ksh libstdc++5
3) unpack the archive
tar  xvf 5.5.1.0-TIV-TSMBAC-LinuxX86.tar
4) unpack the RPM archives (ignore warnings re scripts)
alien  \-g TIVsm-API.i386.rpm
alien  \-g TIVsm-BA.i386.rpm
5) change directory names
mv  TIVsm-API-5.5.1/debian  TIVsm-API-5.5.1/DEBIAN
mv  TIVsm-BA-5.5.1/debian   TIVsm-BA-5.5.1/DEBIAN
6) edit the control files
vim TIVsm-API-5.5.1/DEBIAN/control
\-\- remove blank line after "Maintainer:" line
\-\- in "Architecture:" line change "i386" to "amd64"
\-\- delete "${shlibs:Depends}" in "Depends:" line
\-\- joing two "Description:" lines into one line
\-\- insert line "Version: 5.5.1"
\-\- delete last two lines " ." and " (Converted..."
\-\- append an empty line as last line
\|Source: tivsm-api
\|Section: alien
\|Priority: extra
\|Maintainer: who are you
\|Package: tivsm-api
\|Architecture: amd64
\|Depends:
\|Description: the API IBM Tivoli Storage Manager API
\|Version: 5.5.1
\|
\-\- save and exit
vim TIVsm-BA-5.5.1/DEBIAN/control
\-\- remove blank line after "Maintainer:" line
\-\- in "Architecture:" line change "i386" to "amd64"
\-\- delete "${shlibs:Depends}" in "Depends:" line
\-\- joing two "Description:" lines into one line
\-\- insert line "Version: 5.5.1"
\-\- delete last two lines " ." and " (Converted..."
\-\- append an empty line as last line
\|Source: tivsm-ba
\|Section: alien
\|Priority: extra
\|Maintainer: who are you
\|Package: tivsm-ba
\|Architecture: amd64
\|Depends:
\|Description: the Backup Archive Client IBM Tivoli Storage Manager Client
\|Version: 5.5.1
\|
\-\- save and exit
7) create \*.deb packages
dpkg  \-b TIVsm-API-5.5.1
dpkg  \-b TIVsm-BA-5.5.1
8) install \*.deb packages
dpkg  \-i TIVsm-API-5.5.1.deb
dpkg  \-i TIVsm-BA-5.5.1.deb
9) create/modify TSM configuration files
vim  /opt/tivoli/tsm/client/ba/bin/dsm.opt
\|  ServerName  TSMServer
\|      Domain  ALL-LOCAL
\|  DateFormat  3
\-\- save and exit
vim  /opt/tivoli/tsm/client/ba/bin/dsm.sys
\|        ServerName  TSMServer
\|        CommMethod  TCPip
\|           TcpPort  1500
\|  TcpServerAddress  tsmserver.your.domain.com
\|          NodeName  registered-name-for-this-system
\|    PasswordAccess  generate
\|       Compression  On
\|      ErrorLogName  /var/log/dsmerror.log
\| ErrorLogRetention  5 D
\|      SchedLogName  /var/log/dsmsched.log
\| SchedLogRetention  5 D
\|\*         InclExcl  /opt/tivoli/tsm/client/ba/bin/dsm.inclexcl
\-\- set the TcpServerAddress to the fully qualified name of the TSM Server
\-\- set the NodeName to the node name as registered with the TSM Server
\-\- save and exit
10) run an incremental backup
dsmc  incremental
11) create upstart script
vim  /etc/event.d/dsm-sched
\#  dsm-sched
\#  This service starts the Tivoli Storage Manager "dsmc sched" backup process
\#  and respawns it as the scheduled backup happens or the dsmc process gets
\#  killed or dies.
start on runlevel 2
start on runlevel 3
start on runlevel 4
start on runlevel 5
stop on runlevel 0
stop on runlevel 1
stop on runlevel 6
respawn
exec /usr/bin/dsmc sched &gt;&gt;/tmp/dsm-sched.log 2&gt;&amp;1
\#  end of dsm-sched
\-\- save and exit
12) start the TSM scheduler
start dsm-sched
13) verify the scheduler picked up its schedule
tail  /var/log/dsmsched.log
14)  you are done...
Regards,
Werner</property>
    

<property name="body">h1. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Example contents of dsm.sys file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMmethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu

nodename &lt;servernodename_goeshere&gt; ex. ASPEN
passwordaccess generate
MANAGEDSERVICES	schedule webclient

exclude core
exclude /.../core
exclude /.../tmp/.../*
exclude *_log
exclude *.log
exclude /tmp/*/.../*
exclude /mnt/*/.../*
exclude /.../Cache/*/.../*
exclude /var/run/*/.../*
exclude /var/tmp/*/.../*
exclude /proc/*/.../*
exclude /u0?/oradata/*/.../*
exclude /backup/*/.../*
exclude.dir /proc
exclude.dir /proc/
exclude.dir /dev
exclude.dir /dev/
exclude.dir /mnt
exclude.dir /mnt/
exclude.dir /usr/share/man
exclude dsmsched.log
exclude.dir /var/spool/cups/
exclude.dir /u01/app/sct/suupics
exclude.dir /u01/app/sct/suupics-www
exclude /u01/app/sct/suupics/*
exclude /u01/app/sct/suupics-www/*
{code}

h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc
It will prompt you for your nodename and password.  Once you have entered them, it will drop you at a tsm&gt; prompt.
You can then type 'backup', no quotes, and it will start an incremental backup.  If you don't want to start one right away,
just type 'quit', no quotes, and it will drop you back at the linux prompt.
To start the daemon, run the following command:

#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Server Notes

{code}

Installing TSM Client V5.5.1 on Ubuntu 9.04/amd64
Note: These instructions are based on the report "TSM-Client unter Debian/etch einrichten" at "https://wiki.gw.dg.de/index.php/TSM:debian"
1)  get the RPMs
wget "ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v5r5/Linux/LinuxX86/v551/5.5.1.0-TIV-TSMBAC-LinuxX86.tar"
2)  additional software that may be required (not sure if this is really required, but it works when these are installed)
apt-get install ksh libstdc++5
3) unpack the archive
tar  xvf 5.5.1.0-TIV-TSMBAC-LinuxX86.tar
4) unpack the RPM archives (ignore warnings re scripts)
alien  \-g TIVsm-API.i386.rpm
alien  \-g TIVsm-BA.i386.rpm
5) change directory names
mv  TIVsm-API-5.5.1/debian  TIVsm-API-5.5.1/DEBIAN
mv  TIVsm-BA-5.5.1/debian   TIVsm-BA-5.5.1/DEBIAN
6) edit the control files
vim TIVsm-API-5.5.1/DEBIAN/control
\-\- remove blank line after "Maintainer:" line
\-\- in "Architecture:" line change "i386" to "amd64"
\-\- delete "${shlibs:Depends}" in "Depends:" line
\-\- joing two "Description:" lines into one line
\-\- insert line "Version: 5.5.1"
\-\- delete last two lines " ." and " (Converted..."
\-\- append an empty line as last line
\|Source: tivsm-api
\|Section: alien
\|Priority: extra
\|Maintainer: who are you
\|Package: tivsm-api
\|Architecture: amd64
\|Depends:
\|Description: the API IBM Tivoli Storage Manager API
\|Version: 5.5.1
\|
\-\- save and exit
vim TIVsm-BA-5.5.1/DEBIAN/control
\-\- remove blank line after "Maintainer:" line
\-\- in "Architecture:" line change "i386" to "amd64"
\-\- delete "${shlibs:Depends}" in "Depends:" line
\-\- joing two "Description:" lines into one line
\-\- insert line "Version: 5.5.1"
\-\- delete last two lines " ." and " (Converted..."
\-\- append an empty line as last line
\|Source: tivsm-ba
\|Section: alien
\|Priority: extra
\|Maintainer: who are you
\|Package: tivsm-ba
\|Architecture: amd64
\|Depends:
\|Description: the Backup Archive Client IBM Tivoli Storage Manager Client
\|Version: 5.5.1
\|
\-\- save and exit
7) create \*.deb packages
dpkg  \-b TIVsm-API-5.5.1
dpkg  \-b TIVsm-BA-5.5.1
8) install \*.deb packages
dpkg  \-i TIVsm-API-5.5.1.deb
dpkg  \-i TIVsm-BA-5.5.1.deb
9) create/modify TSM configuration files
vim  /opt/tivoli/tsm/client/ba/bin/dsm.opt
\|  ServerName  TSMServer
\|      Domain  ALL-LOCAL
\|  DateFormat  3
\-\- save and exit
vim  /opt/tivoli/tsm/client/ba/bin/dsm.sys
\|        ServerName  TSMServer
\|        CommMethod  TCPip
\|           TcpPort  1500
\|  TcpServerAddress  tsmserver.your.domain.com
\|          NodeName  registered-name-for-this-system
\|    PasswordAccess  generate
\|       Compression  On
\|      ErrorLogName  /var/log/dsmerror.log
\| ErrorLogRetention  5 D
\|      SchedLogName  /var/log/dsmsched.log
\| SchedLogRetention  5 D
\|\*         InclExcl  /opt/tivoli/tsm/client/ba/bin/dsm.inclexcl
\-\- set the TcpServerAddress to the fully qualified name of the TSM Server
\-\- set the NodeName to the node name as registered with the TSM Server
\-\- save and exit
10) run an incremental backup
dsmc  incremental
11) create upstart script
vim  /etc/event.d/dsm-sched
\#  dsm-sched
\#  This service starts the Tivoli Storage Manager "dsmc sched" backup process
\#  and respawns it as the scheduled backup happens or the dsmc process gets
\#  killed or dies.
start on runlevel 2
start on runlevel 3
start on runlevel 4
start on runlevel 5
stop on runlevel 0
stop on runlevel 1
stop on runlevel 6
respawn
exec /usr/bin/dsmc sched &gt;&gt;/tmp/dsm-sched.log 2&gt;&amp;1
\#  end of dsm-sched
\-\- save and exit
12) start the TSM scheduler
start dsm-sched
13) verify the scheduler picked up its schedule
tail  /var/log/dsmsched.log
14)  you are done...
Regards,
Werner

{code}</property>
    

<property name="body">h1. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Example contents of dsm.sys file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMmethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu

nodename &lt;servernodename_goeshere&gt; ex. ASPEN
passwordaccess generate
MANAGEDSERVICES	schedule webclient

exclude core
exclude /.../core
exclude /.../tmp/.../*
exclude *_log
exclude *.log
exclude /tmp/*/.../*
exclude /mnt/*/.../*
exclude /.../Cache/*/.../*
exclude /var/run/*/.../*
exclude /var/tmp/*/.../*
exclude /proc/*/.../*
exclude /u0?/oradata/*/.../*
exclude /backup/*/.../*
exclude.dir /proc
exclude.dir /proc/
exclude.dir /dev
exclude.dir /dev/
exclude.dir /mnt
exclude.dir /mnt/
exclude.dir /usr/share/man
exclude dsmsched.log
exclude.dir /var/spool/cups/
exclude.dir /u01/app/sct/suupics
exclude.dir /u01/app/sct/suupics-www
exclude /u01/app/sct/suupics/*
exclude /u01/app/sct/suupics-www/*
{code}

h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc
It will prompt you for your nodename and password.  Once you have entered them, it will drop you at a tsm&gt; prompt.
You can then type 'backup', no quotes, and it will start an incremental backup.  If you don't want to start one right away,
just type 'quit', no quotes, and it will drop you back at the linux prompt.
To start the daemon, run the following command:

#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Server Notes

{code}
Installing TSM Client V5.5.1 on Ubuntu 9.04/amd64

Note: These instructions are based on the report "TSM-Client unter Debian/etch einrichten" at "https://wiki.gw.dg.de/index.php/TSM:debian"



1) get the RPMs
wget "ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v5r5/Linux/LinuxX86/v551/5.5.1.0-TIV-TSMBAC-LinuxX86.tar"

2) additional software that may be required (not sure if this is really required, but it works when these are installed)
apt-get install ksh libstdc++5

3) unpack the archive
tar xvf 5.5.1.0-TIV-TSMBAC-LinuxX86.tar

4) unpack the RPM archives (ignore warnings re scripts)
alien -g TIVsm-API.i386.rpm
alien -g TIVsm-BA.i386.rpm

5) change directory names
mv TIVsm-API-5.5.1/debian TIVsm-API-5.5.1/DEBIAN
mv TIVsm-BA-5.5.1/debian TIVsm-BA-5.5.1/DEBIAN

6) edit the control files
vim TIVsm-API-5.5.1/DEBIAN/control
-- remove blank line after "Maintainer:" line
-- in "Architecture:" line change "i386" to "amd64"
-- delete "${shlibs:Depends}" in "Depends:" line
-- joing two "Description:" lines into one line
-- insert line "Version: 5.5.1"
-- delete last two lines " ." and " (Converted..."
-- append an empty line as last line
|Source: tivsm-api
|Section: alien
|Priority: extra
|Maintainer: who are you
|Package: tivsm-api
|Architecture: amd64
|Depends:
|Description: the API IBM Tivoli Storage Manager API
|Version: 5.5.1
|
-- save and exit

vim TIVsm-BA-5.5.1/DEBIAN/control
-- remove blank line after "Maintainer:" line
-- in "Architecture:" line change "i386" to "amd64"
-- delete "${shlibs:Depends}" in "Depends:" line
-- joing two "Description:" lines into one line
-- insert line "Version: 5.5.1"
-- delete last two lines " ." and " (Converted..."
-- append an empty line as last line
|Source: tivsm-ba
|Section: alien
|Priority: extra
|Maintainer: who are you
|Package: tivsm-ba
|Architecture: amd64
|Depends:
|Description: the Backup Archive Client IBM Tivoli Storage Manager Client
|Version: 5.5.1
|
-- save and exit

7) create *.deb packages
dpkg -b TIVsm-API-5.5.1
dpkg -b TIVsm-BA-5.5.1

8) install *.deb packages
dpkg -i TIVsm-API-5.5.1.deb
dpkg -i TIVsm-BA-5.5.1.deb

9) create/modify TSM configuration files
vim /opt/tivoli/tsm/client/ba/bin/dsm.opt
| ServerName TSMServer
| Domain ALL-LOCAL
| DateFormat 3
-- save and exit

vim /opt/tivoli/tsm/client/ba/bin/dsm.sys
| ServerName TSMServer
| CommMethod TCPip
| TcpPort 1500
| TcpServerAddress tsmserver.your.domain.com
| NodeName registered-name-for-this-system
| PasswordAccess generate
| Compression On
| ErrorLogName /var/log/dsmerror.log
| ErrorLogRetention 5 D
| SchedLogName /var/log/dsmsched.log
| SchedLogRetention 5 D
|* InclExcl /opt/tivoli/tsm/client/ba/bin/dsm.inclexcl
-- set the TcpServerAddress to the fully qualified name of the TSM Server
-- set the NodeName to the node name as registered with the TSM Server
-- save and exit

10) run an incremental backup
dsmc incremental

11) create upstart script
vim /etc/event.d/dsm-sched
# dsm-sched

# This service starts the Tivoli Storage Manager "dsmc sched" backup process
# and respawns it as the scheduled backup happens or the dsmc process gets
# killed or dies.

start on runlevel 2
start on runlevel 3
start on runlevel 4
start on runlevel 5

stop on runlevel 0
stop on runlevel 1
stop on runlevel 6

respawn
exec /usr/bin/dsmc sched &gt;&gt;/tmp/dsm-sched.log 2&gt;&amp;1

# end of dsm-sched
-- save and exit

12) start the TSM scheduler
start dsm-sched

13) verify the scheduler picked up its schedule
tail /var/log/dsmsched.log

14) you are done...

Regards,
Werner
{code}</property>
    

<property name="body">h1. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}
h2. Example contents of dsm.sys file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMmethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu

nodename &lt;servernodename_goeshere&gt; ex. ASPEN
passwordaccess generate
MANAGEDSERVICES	schedule webclient

exclude core
exclude /.../core
exclude /.../tmp/.../*
exclude *_log
exclude *.log
exclude /tmp/*/.../*
exclude /mnt/*/.../*
exclude /.../Cache/*/.../*
exclude /var/run/*/.../*
exclude /var/tmp/*/.../*
exclude /proc/*/.../*
exclude /u0?/oradata/*/.../*
exclude /backup/*/.../*
exclude.dir /proc
exclude.dir /proc/
exclude.dir /dev
exclude.dir /dev/
exclude.dir /mnt
exclude.dir /mnt/
exclude.dir /usr/share/man
exclude dsmsched.log
exclude.dir /var/spool/cups/
exclude.dir /u01/app/sct/suupics
exclude.dir /u01/app/sct/suupics-www
exclude /u01/app/sct/suupics/*
exclude /u01/app/sct/suupics-www/*
{code}
h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}
h4. Next, execute the following commands:

{code}
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}
h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc
It will prompt you for your nodename and password.  Once you have entered them, it will drop you at a tsm&gt; prompt.
You can then type 'backup', no quotes, and it will start an incremental backup.  If you don't want to start one right away,
just type 'quit', no quotes, and it will drop you back at the linux prompt.
To start the daemon, run the following command:

#/etc/init.d/suu_tivoli start
{code}
h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}
h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}
h2. Ubuntu Server Notes

{code}
Installing TSM Client V5.5.2 on Ubuntu 9.04 Server 64-bit

Note: These instructions are based on the report "TSM-Client unter Debian/etch einrichten" at "https://wiki.gw.dg.de/index.php/TSM:debian"



1) get the latest client - modify version numbers as needed
wget "ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v5r5/Linux/LinuxX86/v552/5.5.2.0-TIV-TSMBAC-LinuxX86.tar"

2) apt-get install alien ksh libstdc++5 ia32-libs

3) unpack the archive
tar xvf 5.5.2.0-TIV-TSMBAC-LinuxX86.tar

4) unpack the RPM archives (ignore warnings re scripts)
alien -g TIVsm-API.i386.rpm
alien -g TIVsm-BA.i386.rpm

5) change directory names
mv TIVsm-API-5.5.1/debian TIVsm-API-5.5.2/DEBIAN
mv TIVsm-BA-5.5.1/debian TIVsm-BA-5.5.2/DEBIAN

6) edit the control files

vi TIVsm-API-5.5.2/DEBIAN/control
Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-api
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-api
Architecture: amd64
Depends:
Description: the API IBM Tivoli Storage Manager API
Version: 5.5.2
&lt;blank line&gt;

Save and exit the file.

vi TIVsm-BA-5.5.2/DEBIAN/control

Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-ba
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-ba
Architecture: amd64
Depends:
Description: the Backup Archive Client IBM Tivoli Storage Manager Client
Version: 5.5.2
&lt;blank line&gt;

Save and exit the file

7) create *.deb packages
dpkg -b TIVsm-API-5.5.2
dpkg -b TIVsm-BA-5.5.2

8) install *.deb packages
dpkg -i TIVsm-API-5.5.2.deb
dpkg -i TIVsm-BA-5.5.2.deb

9) create/modify TSM configuration files
 (use examples listed above)
vi /opt/tivoli/tsm/client/ba/bin/dsm.opt
vi /opt/tivoli/tsm/client/ba/bin/dsm.sys

10) Run the ldconfig fix located above; run the language fix as well

11) run an incremental backup
dsmc incremental

12) create upstart script
vim /etc/event.d/dsm-sched
# dsm-sched

# This service starts the Tivoli Storage Manager "dsmc sched" backup process
# and respawns it as the scheduled backup happens or the dsmc process gets
# killed or dies.

start on runlevel 2
start on runlevel 3
start on runlevel 4
start on runlevel 5

stop on runlevel 0
stop on runlevel 1
stop on runlevel 6

respawn
exec /usr/bin/dsmc sched &gt;&gt;/tmp/dsm-sched.log 2&gt;&amp;1

# end of dsm-sched
-- save and exit

13) start the TSM scheduler
start dsm-sched
{code}</property>
    

<property name="body">{code}
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 1.0  (buildd@palmer)  Sun Feb  1 20:21:04 UTC 2009

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "Module"
    Load           "dbe"
    Load           "extmod"
    Load           "type1"
    Load           "freetype"
    Load           "glx"
EndSection

Section "ServerFlags"
    Option         "Xinerama" "0"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "DELL 2407WFP"
    HorizSync       30.0 - 83.0
    VertRefresh     56.0 - 76.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce 9800 GT"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "TwinView" "1"
    Option         "metamodes" "DFP-0: nvidia-auto-select +0+0, DFP-1: nvidia-auto-select +1920+0"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection
{code}</property>
    

<property name="body">First off, do not use Tomcat from the Ubuntu repository - download it yourself, and extract it in the home directory of the user it will run as.  The example given here is from our xmlbill server.

h5. Step 1: To make Tomcat start automatically, you must create a file in /etc/init.d called tomcat.  Populate the file with the following:
{code}
#!/bin/bash
#
# Startup script for Tomcat server
#
# chkconfig: - 83 53
# description: Starts and stops the Tomcat daemon.
# processname: tomcat
# pidfile: /var/run/tomcat.pid
export JAVA_HOME=/usr/lib/jvm/java-6-sun
export TOMCAT_HOME=/home/billservice/apps/apache-tomcat-6.0.18

# See how we were called.
case $1 in
        start)

su - billservice -c "sh $TOMCAT_HOME/bin/startup.sh"
        ;;
        stop)
su - billservice -c "sh $TOMCAT_HOME/bin/shutdown.sh"
        ;;
        restart)
su - billservice -c "sh $TOMCAT_HOME/bin/shutdown.sh"
su - billservice -c "sh $TOMCAT_HOME/bin/startup.sh"
        ;;
        *)
                echo "Usage: /etc/init.d/tomcat start|stop|restart"
        ;;
esac

exit 0
{code}

A couple of things to note here; we 'su' to the user we want the process to run as.  This is important because we do NOT want processes running as root.  Additionally, we are explicitly setting the JAVA_HOME environment variable here, but you may wish to set it in /etc/profile (system-wide) or ~.bashrc (user-specific).

h5. Set to start automatically
Run the following commands as root:
{code}
#chmod 755 /etc/init.d/tomcat
#update-rc.d tomcat defaults
{code}
That's it; reboot to verify that everything starts the way you expect.</property>
    

<property name="body">h1. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Example contents of dsm.sys file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMmethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu

nodename &lt;servernodename_goeshere&gt; ex. ASPEN
passwordaccess generate
MANAGEDSERVICES	schedule webclient

exclude core
exclude /.../core
exclude /.../tmp/.../*
exclude *_log
exclude *.log
exclude /tmp/*/.../*
exclude /mnt/*/.../*
exclude /.../Cache/*/.../*
exclude /var/run/*/.../*
exclude /var/tmp/*/.../*
exclude /proc/*/.../*
exclude /u0?/oradata/*/.../*
exclude /backup/*/.../*
exclude.dir /proc
exclude.dir /proc/
exclude.dir /dev
exclude.dir /dev/
exclude.dir /mnt
exclude.dir /mnt/
exclude.dir /usr/share/man
exclude dsmsched.log
exclude.dir /var/spool/cups/
exclude.dir /u01/app/sct/suupics
exclude.dir /u01/app/sct/suupics-www
exclude /u01/app/sct/suupics/*
exclude /u01/app/sct/suupics-www/*
{code}

h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc
It will prompt you for your nodename and password.  Once you have entered them, it will drop you at a tsm&gt; prompt.
You can then type 'backup', no quotes, and it will start an incremental backup.  If you don't want to start one right away,
just type 'quit', no quotes, and it will drop you back at the linux prompt.
To start the daemon, run the following command:

#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Server Notes

{code}
Installing TSM Client V5.5.2 on Ubuntu 9.04 Server 64-bit

Note: These instructions are based on the report "TSM-Client unter Debian/etch einrichten" at "https://wiki.gw.dg.de/index.php/TSM:debian"



1) get the latest client - modify version numbers as needed
wget "ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v5r5/Linux/LinuxX86/v552/5.5.2.0-TIV-TSMBAC-LinuxX86.tar"

2) apt-get install alien ksh libstdc++5 ia32-libs

3) unpack the archive
tar xvf 5.5.2.0-TIV-TSMBAC-LinuxX86.tar

4) unpack the RPM archives (ignore warnings re scripts)
alien -g TIVsm-API.i386.rpm
alien -g TIVsm-BA.i386.rpm

5) change directory names
mv TIVsm-API-5.5.1/debian TIVsm-API-5.5.2/DEBIAN
mv TIVsm-BA-5.5.1/debian TIVsm-BA-5.5.2/DEBIAN

6) edit the control files

vi TIVsm-API-5.5.2/DEBIAN/control
Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-api
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-api
Architecture: amd64
Depends:
Description: the API IBM Tivoli Storage Manager API
Version: 5.5.2
&lt;blank line&gt;

Save and exit the file.

vi TIVsm-BA-5.5.2/DEBIAN/control

Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-ba
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-ba
Architecture: amd64
Depends:
Description: the Backup Archive Client IBM Tivoli Storage Manager Client
Version: 5.5.2
&lt;blank line&gt;

Save and exit the file

7) create *.deb packages
dpkg -b TIVsm-API-5.5.2
dpkg -b TIVsm-BA-5.5.2

8) install *.deb packages
dpkg -i TIVsm-API-5.5.2.deb
dpkg -i TIVsm-BA-5.5.2.deb

9) create/modify TSM configuration files
 (use examples listed above)
vi /opt/tivoli/tsm/client/ba/bin/dsm.opt
vi /opt/tivoli/tsm/client/ba/bin/dsm.sys

10) Run the "Error loading shared libraries" fix located above; run the "English message repository not found" fix as well

11) run an incremental backup
dsmc incremental

12) create upstart script
vim /etc/event.d/dsm-sched
# dsm-sched

# This service starts the Tivoli Storage Manager "dsmc sched" backup process
# and respawns it as the scheduled backup happens or the dsmc process gets
# killed or dies.

start on runlevel 2
start on runlevel 3
start on runlevel 4
start on runlevel 5

stop on runlevel 0
stop on runlevel 1
stop on runlevel 6

respawn
exec /usr/bin/dsmc sched &gt;&gt;/tmp/dsm-sched.log 2&gt;&amp;1

# end of dsm-sched
-- save and exit

13) start the TSM scheduler
start dsm-sched
{code}</property>
    

<property name="body">h1. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Example contents of dsm.sys file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMmethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu

nodename &lt;servernodename_goeshere&gt; ex. ASPEN
passwordaccess generate
MANAGEDSERVICES	schedule webclient

exclude core
exclude /.../core
exclude /.../tmp/.../*
exclude *_log
exclude *.log
exclude /tmp/*/.../*
exclude /mnt/*/.../*
exclude /.../Cache/*/.../*
exclude /var/run/*/.../*
exclude /var/tmp/*/.../*
exclude /proc/*/.../*
exclude /u0?/oradata/*/.../*
exclude /backup/*/.../*
exclude.dir /proc
exclude.dir /proc/
exclude.dir /dev
exclude.dir /dev/
exclude.dir /mnt
exclude.dir /mnt/
exclude.dir /usr/share/man
exclude dsmsched.log
exclude.dir /var/spool/cups/
exclude.dir /u01/app/sct/suupics
exclude.dir /u01/app/sct/suupics-www
exclude /u01/app/sct/suupics/*
exclude /u01/app/sct/suupics-www/*
{code}

h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
FOR UBUNTU SERVER:
update-rc.d suu_tivoli defaults

FOR RED HAT:
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc
It will prompt you for your nodename and password.  Once you have entered them, it will drop you at a tsm&gt; prompt.
You can then type 'backup', no quotes, and it will start an incremental backup.  If you don't want to start one right away,
just type 'quit', no quotes, and it will drop you back at the linux prompt.
To start the daemon, run the following command:

#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Server Notes

{code}
Installing TSM Client V5.5.2 on Ubuntu 9.04 Server 64-bit

Note: These instructions are based on the report "TSM-Client unter Debian/etch einrichten" at "https://wiki.gw.dg.de/index.php/TSM:debian"



1) get the latest client - modify version numbers as needed
wget "ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v5r5/Linux/LinuxX86/v552/5.5.2.0-TIV-TSMBAC-LinuxX86.tar"

2) apt-get install alien ksh libstdc++5 ia32-libs

3) unpack the archive
tar xvf 5.5.2.0-TIV-TSMBAC-LinuxX86.tar

4) unpack the RPM archives (ignore warnings re scripts)
alien -g TIVsm-API.i386.rpm
alien -g TIVsm-BA.i386.rpm

5) change directory names
mv TIVsm-API-5.5.1/debian TIVsm-API-5.5.2/DEBIAN
mv TIVsm-BA-5.5.1/debian TIVsm-BA-5.5.2/DEBIAN

6) edit the control files

vi TIVsm-API-5.5.2/DEBIAN/control
Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-api
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-api
Architecture: amd64
Depends:
Description: the API IBM Tivoli Storage Manager API
Version: 5.5.2
&lt;blank line&gt;

Save and exit the file.

vi TIVsm-BA-5.5.2/DEBIAN/control

Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-ba
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-ba
Architecture: amd64
Depends:
Description: the Backup Archive Client IBM Tivoli Storage Manager Client
Version: 5.5.2
&lt;blank line&gt;

Save and exit the file

7) create *.deb packages
dpkg -b TIVsm-API-5.5.2
dpkg -b TIVsm-BA-5.5.2

8) install *.deb packages
dpkg -i TIVsm-API-5.5.2.deb
dpkg -i TIVsm-BA-5.5.2.deb

9) create/modify TSM configuration files
 (use examples listed above)
vi /opt/tivoli/tsm/client/ba/bin/dsm.opt
vi /opt/tivoli/tsm/client/ba/bin/dsm.sys

10) Run the "Error loading shared libraries" fix located above; run the "English message repository not found" fix as well

11) run an incremental backup
dsmc incremental

12) create upstart script
vim /etc/event.d/dsm-sched
# dsm-sched

# This service starts the Tivoli Storage Manager "dsmc sched" backup process
# and respawns it as the scheduled backup happens or the dsmc process gets
# killed or dies.

start on runlevel 2
start on runlevel 3
start on runlevel 4
start on runlevel 5

stop on runlevel 0
stop on runlevel 1
stop on runlevel 6

respawn
exec /usr/bin/dsmc sched &gt;&gt;/tmp/dsm-sched.log 2&gt;&amp;1

# end of dsm-sched
-- save and exit

13) start the TSM scheduler
start dsm-sched
{code}</property>
    

<property name="body">h2. First Step
h5. If IP is assigned by DHCP, make sure /etc/hosts file looks like this:
{code:title=/etc/hosts|borderStyle=solid}
127.0.0.1     servername.suu.edu     localhost.localdomain     localhost     servername
{code}
h5. If IP is hard-coded, make sure /etc/hosts file looks like this (x.x is your new IP):
{code:title=/etc/hosts|borderStyle=solid}
127.0.0.1     localhost.localdomain     localhost
134.250.x.x   yourserver.suu.edu        yourserver
{code}

h2. Second Step
h5. If you need the change to happen immediately without a reboot, run the following command as root:
{code:borderStyle=solid}
#hostname yourserver.suu.edu
{code}
h2. Third Step
h5. This step is optional, and depends on the linux distribution and version you are using.  If you have an /etc/HOSTNAME file, ensure that it is populated with a single line as follows:
{code:borderStyle=solid}
yourserver.suu.edu
{code}
h2. Fourth Step
h5. Edit the /etc/sysconfig/network file HOSTNAME line to read:
{code:title=/etc/sysconfig/network|borderStyle=solid}
HOSTNAME=yourserver.suu.edu
{code}
h2. Fifth Step
h5. As root, run the following command:
{code:borderStyle=solid}
#echo yourserver.suu.edu &gt; /proc/sys/kernel/hostname

To verify that it worked, run:
#cat /proc/sys/kernel/hostname
{code}
h2. Finally, reboot.
</property>
    

<property name="body">&lt;ol&gt;&lt;li&gt;Physically put the disk in the server&amp;nbsp; or create a new virtual disk for the VM &amp;nbsp;(add it to a NEW controller, i.e. scsi 1:0, 2:0, 3:0 and it will detect it without a reboot)&lt;/li&gt;&lt;li&gt;Find the identifier of the new disk by running 'dmesg |grep sd' at the command line. &amp;nbsp;The newest one should be the last one in the list (i.e. sdb, sdc, etc.); use fdisk to create new partition on the disk.&lt;/li&gt;&lt;li&gt;Extend existing volume group onto new partition.&lt;/li&gt;&lt;li&gt;Extend existing logical volume onto new space.&lt;/li&gt;&lt;li&gt;Extend filesystem.&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;For this example we are going to assume that our new disk that has been added to our server is /dev/sdc. We will also assume that we have a volume group named VolGroup00 and a logical volume on that volume group named BACKUP. Also in this example, /dev/mapper/VolGroup00-BACKUP is mounted on our Linux system as /backup. Let's get started.&lt;/p&gt;&lt;ol&gt;&lt;li&gt;fdisk /dev/sdc&lt;/li&gt;&lt;li&gt;n&lt;/li&gt;&lt;li&gt;p&lt;/li&gt;&lt;li&gt;1 &amp;lt;Enter&amp;gt; &amp;lt;Enter&amp;gt; &amp;nbsp;(twice)&lt;/li&gt;&lt;li&gt;t&lt;/li&gt;&lt;li&gt;8e&lt;/li&gt;&lt;li&gt;w&lt;/li&gt;&lt;li&gt;pvcreate /dev/sdc1&lt;/li&gt;&lt;li&gt;vgdisplay (to get volgroupname)&lt;/li&gt;&lt;li&gt;vgextend &amp;lt;volgroupname&amp;gt; /dev/sdc1&lt;/li&gt;&lt;li&gt;lvdisplay (to get name of logical volume you want to extend)&lt;/li&gt;&lt;li&gt;lvextend -L +10G /dev/mapper/&amp;lt;lvname&amp;gt; &amp;nbsp;/dev/sdc1 &amp;nbsp;(this will extend the volume by 10 gigabytes. &amp;nbsp;If you want to use the whole disk, just take out the -L +10G part)&lt;/li&gt;&lt;li&gt;resize2fs /dev/mapper/&amp;lt;lvname&amp;gt;&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;Done - verify new size&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;COMMAND-LINE OPTIONS:&lt;/p&gt;&lt;p&gt;fdisk /dev/xvdf&lt;/p&gt;&lt;p&gt;pvcreate /dev/xvdf1&lt;/p&gt;&lt;p&gt;vgcreate mvg /dev/xvdf1&lt;br /&gt;lvcreate -L 8192M -n tmpvol mvg&lt;br /&gt;lvcreate -L 8192M -n swapvol mvg&lt;br /&gt;lvcreate -L 2048M -n homevol mvg&lt;br /&gt;lvcreate -L 5G -n varvol mvg&lt;br /&gt;pvdisplay (to get free PE)&lt;br /&gt;lvcreate -l &amp;lt;freePEval&amp;gt; -n u01vol mvg&lt;br /&gt;mkfs.ext4 /dev/mapper/mvg-u01vol&lt;/p&gt;</property>
    

<property name="body"># Physically put the disk in the server&amp;nbsp; or create a new virtual disk for the VM
# Use fdisk to create new partition on the disk.
# Extend existing volume group onto new partition.
# Extend existing logical volume onto new space.
# Extend filesystem.

I'll go into more detail how to do each of these steps on SLES and RHEL. For this example we are going to assume that our new disk that has been added to our server is /dev/sdc. We will also assume that we have a volume group named rootvg and a logical volume on that volume group named homelv. Also in this example, /dev/rootvg/homelv is mounted on our Linux system as /home. Let's get started.

# Physically put the disk in the server and make it available either in an array or some other way.
#* This can vary widely depending on what hardware you are on, so we will not cover this portion in this tutorial. You may want to use [Google|http://www.google.com/] to search for how to do this on your hardware.
# Use fdisk to create new partition on the disk.
#* As root run fdisk on the new disk. For example you would run fdisk /dev/sdc.
#* On this new disk you will create a new partition. Inside of the fdisk program you create a new partition by typing the letter "n" followed by the enter key.
#* It will then ask you if you want it to be a primary partition or an extended partition. For this example we will just assume we want it to be a primary partition. To do this we type the letter "p" followed by the enter key.
#* Next it will ask for the starting point and ending point of this partition. For this example, we will simply select the defaults by hitting the enter key twice.
#* If you want to view the details of the new partition, you can type the letter "p" from the fdisk prompt.
#* Next we need to change the type for this new partition. We do this by typing the letter "t" followed by the enter key.
#* It asks to enter in what type we want it to be. We need it to be of the Linux LVM type. The Hex code for Linux LVM is 8e. We type in "8e" followed by the enter key and it will tell us that it changed the system type for this partition to Linux LVM.
#* We then need to save these changes and exit fdisk. We do this by typing the letter "w" (for write) followed by the enter key.
# Use pvcreate to lay down the "setup" on the physical partition.
#* This sets up physical extents and other things that LVM needs. The command we run is "pvcreate /dev/sdc1"
# Extend existing volume group onto new partition.
#* For this example we are going to assume that we have an existing volume group named rootvg. We can display information about this volume group using the vgdisplay command. If we type "vgdisplay" without any arguments, it will display all the volume groups. If we just want information about the "rootvg" volume group, we would type "vgdisplay rootvg".
#* To extend the rootvg volume group onto the new partition, we use the vgextend command. Type "vgextend rootvg /dev/sdc1" followed by the enter key. This will extend the rootvg volume group onto the new partition, /dev/sdc1.
# Extend existing logical volume onto new space.
#* For this example we are going to assume that we have an existing logical volume on the rootvg volume group that is named homelv. The full path to this logical volume would be "/dev/rootvg/homelv". We can view information about this logical volume by typing "lvdisplay /dev/rootvg/homelv".
#* To extend this existing logical volume onto the new space we use the lvextend command. Type "lvextend \-L \+20G /dev/rootvg/homelv /dev/sdc1". This command says that we want to increase the /dev/rootvg/homelv logical volume by 20GB. This is only possible if /dev/sdc1 is a member of volume group rootvg and there is enough free disk space on it.
# The last thing we need to do is increase the filesystem.
#* Which command we use to increase the filesystem depends on what filesystem type we are currently using. If we are using reiserfs, we will use the "resize_reiserfs" command. If we are using ext3, we will use either the "ext2online" or the "resize2fs" command. On RHEL 5, we can use the "resize2fs" command, which will recognize that the filesystem is currently mounted and perform an "on-line" resize.
#* On both resize_reiserfs and ext2online, the size is optional. If we want the filesystem to take up all the available space on our logical volume, we don't need to put the size. To extend the filesystem type either "ext2online /dev/rootvg/homelv" or "resize2fs /dev/rootvg/homelv".</property>
    

<property name="body">&lt;p&gt;Since the Ecommerce subnet is very locked down, we have to take a couple of extra steps to enable hosts to talk to each other even though they are in the same subnet.&lt;/p&gt;

&lt;p&gt;For Ubuntu Server:&lt;/p&gt;

&lt;p&gt;edit the /etc/rc.local file, and put the following lines just before the last line:&lt;/p&gt;

&lt;p&gt;For the host you want to connect TO:&lt;/p&gt;


&lt;p&gt;exec arp -s &amp;lt;ipaddress&amp;gt;&amp;lt;space&amp;gt;&amp;lt;macaddress&amp;gt;&lt;/p&gt;

&lt;p&gt;For the host you are ON: (optional; I like this for documentation purposes)&lt;/p&gt;


&lt;p&gt;exec arp -s &amp;lt;ipaddress&amp;lt;space&amp;gt;&amp;lt;macaddress&amp;gt;&lt;/p&gt;

&lt;p&gt;Save the file, and then make sure it is flagged executable.&lt;/p&gt;

&lt;p&gt;That's it - on next reboot, you should be able to communicate with the remote box.&lt;/p&gt;</property>
    

<property name="body">{code}
The key to creating self-signing certificates in Tomcat is to remember the key files/components involved:
&lt;yourkeystore&gt; and cacerts, and an existing Java HOME variable.


&lt;yourkeystore&gt; will be whatever you decide to call it when creating the self-signed certificate.  For example, the following
command creates a keystore called mykeystore with an alias of tomcat and a validity of 10 years in the C:\ssl directory:

%JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA -keystore C:\ssl\mykeystore -validity 3650
remember first and last name must be the host+domain, i.e. tntrans.suu.edu

Export it:
%JAVA_HOME%\bin\keytool -export -alias tomcat -file D:\ssl\exported.cert -keystore C:\ssl\mykeystore

Once created, then you must import it into your existing CACERTS file for it to be 'trusted':

%JAVA_HOME%\bin\keytool -import -alias tomcat -trustcacerts -file D:\SSL\exported.cert -keystore %JAVA_HOME%\jre\lib\security\cacerts (this pass will be changeit)
{code}
On the ipsca website:

{color:#333333}&amp;nbsp;{color}{color:#333333}&amp;nbsp;{color}
| {color:#2c63ca}&amp;nbsp;Certificate installation{color} | \\ |
{color:#333333}Installing your Certificate with Jakarta-Tomcat.{color}
{color:#333333}(For Linux &amp; Windows){color}{color:#333333}&amp;nbsp;{color}
| {color:#333333}This document explains how to generate and install a Server Digital Certificate, and answers any question you might have.{color} || {color:#333333}{*}Creating a Certificate Signing Request{*}{color}\\ |
| {color:#333333}Follow these instructions to generate a CSR for your Web site. When you have completed this process, you will have a CSR ready to submit to{color}{color:#333333}&amp;nbsp;{color}ipsCA{color:#333333}&amp;nbsp;{color}{color:#333333}in order to be generated into a SSL Security Certificate.{color}\\ {color:#333333}If you are not using JDK 1.4 or higher, you must download and install "Java Secure Socket Extensions" JSSE.{color}\\ {color:#333333}1. Generate a private key with the following command:{color}\\ {color:#333333}*$JAVA_HOME/bin/keytool \-genkey \-alias tomcat \-keyalg RSA \-keystore /path/to/domainname.kdb*{color}\\ {color:#333333}You will be prompted for a password. Tomcat uses a default password of "changeit". If you use a different password, you will need to specify a custom password in the server.xml configuration file.{color}\\ {color:#333333}In the next field you will be asked "What is your first and last name?" At this prompt, you must specify the common name (FQDN) of your web site.{color}\\ {color:#333333}You will then be prompted for your organizational unit, organization, etc.{color}\\ {color:#333333}.2. Generate the Certificate Signing Request (CSR){color}\\ {color:#333333}*$JAVA_HOME/bin/keytool \-certreq \-alias tomcat \-keystore /path/to/keystore.kdb \-file filename.csr*{color}\\ {color:#333333}You will not be prompted for the common name, organization, etc. The keytool will use the values that you specify when generating the private key.{color}\\ {color:#333333}3. Now go to{color}{color:#333333}&amp;nbsp;{color}ipsCA{color:#333333}&amp;nbsp;{color}{color:#333333}, select your certificate and fill in the form with your personal data, paste your certificate request in the CSR field and make sure that you include \---\-{color}{color:#333333}{-}BEGIN NEW CERTIFICATE REQUEST{-}{color}{color:#333333}\-\-{color}{color:#333333}-\- and --{color}{color:#333333}\-\-{color}{color:#333333}{-}END NEW CERTIFICATE REQUEST{-}{color}{color:#333333}\----.{color}\\ {color:#333333}4. Make a backup of the keystore.kdb key database. It would be useful for you if your server crashes.{color}\\ | |
| {color:#333333}{*}Installing a Server Digital Certificate{*}{color}\\ |
| {color:#333333}{*}Upload a New SSL Certificate{*}{color}\\ {color:#333333}After you receive your certificate,{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}two other certificates will be necessary to setup your SSL Server, IPS SERVIDORES ROOT CERTIFICATE and the intermediate CA IPSCA CLASEA1{*}{color}{color:#333333}.{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}It is essential that these certificates are also&amp;nbsp; installed on your webserver in order to establish correct SSL connections{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}with your customer's browsers. Should they be required, you may download these certificates individually or collectively as a bundled file below:{color}\\
IPSServidores.crt \\
IPSCACLASEA1.crt \\
IPS-IPSCABUNDLE.CRT \\ {color:#333333}You must first export the certificates in the following format:{color}
# {color:#333333}Copy the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{_}IPSCACLASEA1 Chained CA certificate{_}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}into a text editor such as notepad and save as{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{_}chain.cer{_}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}on a Windows machine with IE 5+.{color}
# {color:#333333}Copy your{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{_}web server certificate{_}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}into a text editor such as notepad and save as{color}{color:#333333}{_}yourdomain.cer{_}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}on a Windows machine with IE 5+.{color}
# {color:#333333}Copy the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{_}IPSServidores root CA{_}{color}{color:#333333}_&amp;nbsp;_{color}{color:#333333}{_}certificate{_}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}into a text editor and save as{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{_}root.cer{_}{color}{color:#333333}_&amp;nbsp;_{color}{color:#333333}on a Windows machine with IE 5+.{color}
# {color:#333333}Double-click the root.cer and select the Details tab, then Copy to File, then select the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}Base-64{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}option, give your copied certificate a file name of{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}root_der.cer{*}{color}
# {color:#333333}Double-click the chain.cer and select Install. Choose "Place all certificates in following store" and select Intermediate Certification Authorities. Complete the Wizard.{color}
# {color:#333333}Double-click the chain.cer again and select the Details tab, then Copy to File, then select the{color}{color:#333333}{*}Base-64{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}option, give your copied certificate a file name of{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}chain_der.cer{*}{color}
# {color:#333333}Double click the youdomain.cer and select the Details tab, then Copy to File, then select the{color}{color:#333333}{*}PKCS#7 (p7b)*{color}{color:#333333}&amp;nbsp;{color}{color:#333333}option, also select the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}Include all certificates in the certification path{*}{color}{color:#333333}, give your copied certificate a file name of{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}yourdomain.p7b{*}{color}{color:#333333}{*}The following certificate installations must be executed in the stated order.*{color}\\ {color:#333333}1. Import the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}root_der.cer{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}and{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}chain_der.cer{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}files using:{color}{color:#333333}*$ keytool \-import \-trustcacerts \-keystore my.kdb \-alias root - file root_der.cer{*}{color}\\ {color:#333333}*$ keytool \-import \-trustcacerts \-keystore my.kdb \-alias chain - file chain_der.cer*{*}{color}{color:#333333}With my.kdb being your keystore.{color}\\ {color:#333333}2. Import the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}yourdomain.p7b file{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}using:{color}{color:#333333}{*}*keytool \-import \-trustcacerts \-keystore my.kdb \-alias tomcat \-file yourdomain.p7b*{*}{color}{color:#333333}With my.kdb being your keystore.{color}\\ {color:#333333}&amp;nbsp;{color}\\ {color:#333333}{*}Update server.xml configuration{color} {color:#333333}[file:*]{color}\\ {color:#333333}1. Open "$JAKARTA_HOME/conf/server.xml" in a text editor.{color}\\ {color:#333333}2. Find the following section:{color}\\ {color:#333333}&lt;Connector{color}{color:#333333}&amp;nbsp;{color}\\ {color:#333333}...{color}{color:#333333}&amp;nbsp;{color}\\ {color:#333333}scheme="https"{color}{color:#333333}&amp;nbsp;{color}\\ {color:#333333}secure="true"{color}{color:#333333}&amp;nbsp;{color}\\ {color:#333333}keystoreFile="/pathto/my.kdb"{color}{color:#333333}&amp;nbsp;{color}\\ {color:#333333}keystorePass="mypassword"{color}\\ {color:#333333}3. If you want Tomcat to use the default SSL port, change all instances of the port number 8443 to 443.{color}\\ {color:#333333}4. Add the keystoreFile and keystorePass directives to correspond with the keystore file and password that you are using.{color}\\ {color:#333333}5. Start or restart Tomcat using the appropriate startup script (startup.sh for unix/linux or startup.bat for windows){color} | |</property>
    

<property name="body">{code}The key to creating self-signed certificates in Tomcat is to remember the key files/components involved:
&lt;yourkeystore&gt; and cacerts, and an existing Java HOME variable.


&lt;yourkeystore&gt; will be whatever you decide to call it when creating the self-signed certificate.  For example, the following
command creates a keystore called mykeystore with an alias of tomcat and a validity of 10 years in the C:\ssl directory:

%JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA -keystore C:\ssl\mykeystore -validity 3650
remember first and last name must be the host+domain, i.e. tntrans.suu.edu

Export it:
%JAVA_HOME%\bin\keytool -export -alias tomcat -file D:\ssl\exported.cert -keystore C:\ssl\mykeystore

Once created, then you must import it into your existing CACERTS file for it to be 'trusted':

%JAVA_HOME%\bin\keytool -import -alias tomcat -trustcacerts -file D:\SSL\exported.cert -keystore %JAVA_HOME%\jre\lib\security\cacerts (this pass will be changeit)
{code}On the ipsca website:

{color:#333333}&amp;nbsp;{color}{color:#333333}&amp;nbsp;{color}
| {color:#2c63ca}&amp;nbsp;Certificate installation{color} | \\ |
{color:#333333}Installing your Certificate with Jakarta-Tomcat.{color}
{color:#333333}(For Linux &amp; Windows){color}{color:#333333}&amp;nbsp;{color}
| {color:#333333}This document explains how to generate and install a Server Digital Certificate, and answers any question you might have.{color} || {color:#333333}{*}Creating a Certificate Signing Request{*}{color}\\ |
| {color:#333333}Follow these instructions to generate a CSR for your Web site. When you have completed this process, you will have a CSR ready to submit to{color}{color:#333333}&amp;nbsp;{color}ipsCA{color:#333333}&amp;nbsp;{color}{color:#333333}in order to be generated into a SSL Security Certificate.{color}\\  {color:#333333}If you are not using JDK 1.4 or higher, you must download and install "Java Secure Socket Extensions" JSSE.{color}\\  {color:#333333}1. Generate a private key with the following command:{color}\\  {color:#333333}*$JAVA_HOME/bin/keytool \-genkey \-alias tomcat \-keyalg RSA \-keystore /path/to/domainname.kdb{*}{color}\\  {color:#333333}You will be prompted for a password. Tomcat uses a default password of "changeit". If you use a different password, you will need to specify a custom password in the server.xml configuration file.{color}\\  {color:#333333}In the next field you will be asked "What is your first and last name?" At this prompt, you must specify the common name (FQDN) of your web site.{color}\\  {color:#333333}You will then be prompted for your organizational unit, organization, etc.{color}\\  {color:#333333}.2. Generate the Certificate Signing Request (CSR){color}\\  {color:#333333}*$JAVA_HOME/bin/keytool \-certreq \-alias tomcat \-keystore /path/to/keystore.kdb \-file filename.csr{*}{color}\\  {color:#333333}You will not be prompted for the common name, organization, etc. The keytool will use the values that you specify when generating the private key.{color}\\  {color:#333333}3. Now go to{color}{color:#333333}&amp;nbsp;{color}ipsCA{color:#333333}&amp;nbsp;{color}{color:#333333}, select your certificate and fill in the form with your personal data, paste your certificate request in the CSR field and make sure that you include \---\-{color}{color:#333333}{-}BEGIN NEW CERTIFICATE REQUEST{-}{color}{color:#333333}\-\-{color}{color:#333333}\-\- and --{color}{color:#333333}\-\-{color}{color:#333333}{-}END NEW CERTIFICATE REQUEST{-}{color}{color:#333333}\----.{color}\\  {color:#333333}4. Make a backup of the keystore.kdb key database. It would be useful for you if your server crashes.{color}\\ | |
| {color:#333333}{*}Installing a Server Digital Certificate{*}{color}\\ |
| {color:#333333}{*}Upload a New SSL Certificate{*}{color}\\  {color:#333333}After you receive your certificate,{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}two other certificates will be necessary to setup your SSL Server, IPS SERVIDORES ROOT CERTIFICATE and the intermediate CA IPSCA CLASEA1{*}{color}{color:#333333}.{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}It is essential that these certificates are also&amp;nbsp; installed on your webserver in order to establish correct SSL connections{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}with your customer's browsers. Should they be required, you may download these certificates individually or collectively as a bundled file below:{color}\\
IPSServidores.crt \\
IPSCACLASEA1.crt \\
IPS-IPSCABUNDLE.CRT \\  {color:#333333}You must first export the certificates in the following format:{color}
# {color:#333333}Copy the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{_}IPSCACLASEA1 Chained CA certificate{_}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}into a text editor such as notepad and save as{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{_}chain.cer{_}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}on a Windows machine with IE 5+.{color}
# {color:#333333}Copy your{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{_}web server certificate{_}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}into a text editor such as notepad and save as{color}{color:#333333}{_}yourdomain.cer{_}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}on a Windows machine with IE 5+.{color}
# {color:#333333}Copy the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{_}IPSServidores root CA{_}{color}{color:#333333}_&amp;nbsp;_{color}{color:#333333}{_}certificate{_}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}into a text editor and save as{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{_}root.cer{_}{color}{color:#333333}_&amp;nbsp;_{color}{color:#333333}on a Windows machine with IE 5+.{color}
# {color:#333333}Double-click the root.cer and select the Details tab, then Copy to File, then select the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}Base-64{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}option, give your copied certificate a file name of{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}root_der.cer{*}{color}
# {color:#333333}Double-click the chain.cer and select Install. Choose "Place all certificates in following store" and select Intermediate Certification Authorities. Complete the Wizard.{color}
# {color:#333333}Double-click the chain.cer again and select the Details tab, then Copy to File, then select the{color}{color:#333333}{*}Base-64{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}option, give your copied certificate a file name of{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}chain_der.cer{*}{color}
# {color:#333333}Double click the youdomain.cer and select the Details tab, then Copy to File, then select the{color}{color:#333333}{*}PKCS#7 (p7b)*{color}{color:#333333}&amp;nbsp;{color}{color:#333333}option, also select the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}Include all certificates in the certification path{*}{color}{color:#333333}, give your copied certificate a file name of{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}yourdomain.p7b{*}{color}{color:#333333}{*}The following certificate installations must be executed in the stated order.*{color}\\  {color:#333333}1. Import the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}root_der.cer{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}and{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}chain_der.cer{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}files using:{color}{color:#333333}*$ keytool \-import \-trustcacerts \-keystore my.kdb \-alias root - file root_der.cer{*}{color}\\  {color:#333333}*$ keytool \-import \-trustcacerts \-keystore my.kdb \-alias chain - file chain_der.cer{*}{color}{color:#333333}{*}{color}{color:#333333}With my.kdb being your keystore.{color}\\  {color:#333333}2. Import the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}yourdomain.p7b file{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}using:{color}{color:#333333}{*}{color}{color:#333333}{*}keytool \-import \-trustcacerts \-keystore my.kdb \-alias tomcat \-file yourdomain.p7b{*}{color}{color:#333333}{*}{color}{color:#333333}With my.kdb being your keystore.{color}\\  {color:#333333}&amp;nbsp;{color}\\  {color:#333333}{*}Update server.xml configuration{color} {color:#333333}[file:\*|file:*]{color}\\  {color:#333333}1. Open "$JAKARTA_HOME/conf/server.xml" in a text editor.{color}\\  {color:#333333}2. Find the following section:{color}\\  {color:#333333}&lt;Connector{color}{color:#333333}&amp;nbsp;{color}\\  {color:#333333}...{color}{color:#333333}&amp;nbsp;{color}\\  {color:#333333}scheme="https"{color}{color:#333333}&amp;nbsp;{color}\\  {color:#333333}secure="true"{color}{color:#333333}&amp;nbsp;{color}\\  {color:#333333}keystoreFile="/pathto/my.kdb"{color}{color:#333333}&amp;nbsp;{color}\\  {color:#333333}keystorePass="mypassword"{color}\\  {color:#333333}3. If you want Tomcat to use the default SSL port, change all instances of the port number 8443 to 443.{color}\\  {color:#333333}4. Add the keystoreFile and keystorePass directives to correspond with the keystore file and password that you are using.{color}\\  {color:#333333}5. Start or restart Tomcat using the appropriate startup script (startup.sh for unix/linux or startup.bat for windows){color} | |</property>
    

<property name="body">{code}The key to creating self-signed certificates in Tomcat is to remember the key files/components involved:
&lt;yourkeystore&gt; and cacerts, and an existing Java HOME variable.


&lt;yourkeystore&gt; will be whatever you decide to call it when creating the self-signed certificate.  For example, the following
command creates a keystore called mykeystore with an alias of tomcat and a validity of 10 years in the C:\ssl directory:

%JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA -keystore C:\ssl\mykeystore -validity 3650
remember first and last name must be the host+domain, i.e. tntrans.suu.edu

Export it:
%JAVA_HOME%\bin\keytool -export -alias tomcat -file D:\ssl\exported.cert -keystore C:\ssl\mykeystore

Once created, then you must import it into your existing CACERTS file for it to be 'trusted':

%JAVA_HOME%\bin\keytool -import -alias tomcat -trustcacerts -file D:\SSL\exported.cert -keystore %JAVA_HOME%\jre\lib\security\cacerts (this pass will be changeit)
{code}{color:#333333}Installing your Certificate with Jakarta-Tomcat.{color}
{color:#333333}(For Linux &amp; Windows){color}{color:#333333}&amp;nbsp;{color}
| {color:#333333}This document explains how to generate and install a Server Digital Certificate, and answers any question you might have.{color} || {color:#333333}{*}Creating a Certificate Signing Request{*}{color}\\ |
| {color:#333333}1. Generate a private key with the following command:{color}\\  {color:#333333}*$JAVA_HOME/bin/keytool \-genkey \-alias tomcat \-keyalg RSA \-validity 730 \-keystore /path/to/domainname.kdb{*}{color}\\  \\
{color:#333333}You will be prompted for a password. Tomcat uses a default password of "changeit" - do NOT use that. If you use a different password, you will need to specify a custom password in the server.xml configuration file.{color}\\  \\
{color:#333333}In the next field you will be asked "What is your first and last name?" At this prompt, you must specify the common name (FQDN) of your web site.{color}\\  {color:#333333}You will then be prompted for your organizational unit, organization, etc.{color}\\  \\
{color:#333333}2. Generate the Certificate Signing Request (CSR){color}\\  {color:#333333}*$JAVA_HOME/bin/keytool \-certreq \-alias tomcat \-keystore /path/to/keystore.kdb \-file servername.csr{*}{color}\\  \\  {color:#333333}3. Now go to{color}{color:#333333}&amp;nbsp;{color}ipsCA{color:#333333}&amp;nbsp;{color}{color:#333333}, select your certificate and fill in the form with your personal data, paste your certificate request in the CSR field and make sure that you include BEGIN NEW CERTIFICATE REQUEST and END NEW CERTIFICATE REQUEST in your copied text.{color}\\
\\  {color:#333333}4. Make a backup of the keystore.kdb key database. It would be useful for you if your server crashes.{color}\\ | |
| {color:#333333}{*}Installing a Server Digital Certificate{*}{color}\\ |
| {color:#333333}{*}Upload a New SSL Certificate{*}{color}\\  {color:#333333}After you receive your certificate,{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}two other certificates will be necessary to setup your SSL Server, IPS SERVIDORES ROOT CERTIFICATE and the intermediate CA IPSCA CLASEA1{*}{color}{color:#333333}.{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}It is essential that these certificates are also&amp;nbsp; installed on your webserver in order to establish correct SSL connections{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}with your customer's browsers. Should they be required, you may download these certificates individually or collectively as a bundled file below:{color}\\
IPSServidores.crt \\
IPSCACLASEA1.crt \\
IPS-IPSCABUNDLE.CRT \\  {color:#333333}You must first export the certificates in the following format:{color}
# {color:#333333}Copy the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{_}IPSCACLASEA1 Chained CA certificate{_}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}into a text editor such as notepad and save as{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{_}chain.cer{_}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}on a Windows machine with IE 5+.{color}
# {color:#333333}Copy your{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{_}web server certificate{_}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}into a text editor such as notepad and save as{color}{color:#333333}{_}yourdomain.cer{_}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}on a Windows machine with IE 5+.{color}
# {color:#333333}Copy the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{_}IPSServidores root CA{_}{color}{color:#333333}_&amp;nbsp;_{color}{color:#333333}{_}certificate{_}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}into a text editor and save as{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{_}root.cer{_}{color}{color:#333333}_&amp;nbsp;_{color}{color:#333333}on a Windows machine with IE 5+.{color}
# {color:#333333}Double-click the root.cer and select the Details tab, then Copy to File, then select the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}Base-64{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}option, give your copied certificate a file name of{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}root_der.cer{*}{color}
# {color:#333333}Double-click the chain.cer and select Install. Choose "Place all certificates in following store" and select Intermediate Certification Authorities. Complete the Wizard.{color}
# {color:#333333}Double-click the chain.cer again and select the Details tab, then Copy to File, then select the{color}{color:#333333}{*}Base-64{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}option, give your copied certificate a file name of{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}chain_der.cer{*}{color}
# {color:#333333}Double click the youdomain.cer and select the Details tab, then Copy to File, then select the{color}{color:#333333}{*}PKCS#7 (p7b)*{color}{color:#333333}&amp;nbsp;{color}{color:#333333}option, also select the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}Include all certificates in the certification path{*}{color}{color:#333333}, give your copied certificate a file name of{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}yourdomain.p7b{*}{color}{color:#333333}{*}The following certificate installations must be executed in the stated order.*{color}\\  {color:#333333}1. Import the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}root_der.cer{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}and{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}chain_der.cer{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}files using:{color}{color:#333333}*$ keytool \-import \-trustcacerts \-keystore my.kdb \-alias root - file root_der.cer{*}{color}\\  {color:#333333}*$ keytool \-import \-trustcacerts \-keystore my.kdb \-alias chain - file chain_der.cer{*}{color}{color:#333333}{*}{color}{color:#333333}With my.kdb being your keystore.{color}\\  {color:#333333}2. Import the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}yourdomain.p7b file{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}using:{color}{color:#333333}{*}{color}{color:#333333}{*}keytool \-import \-trustcacerts \-keystore my.kdb \-alias tomcat \-file yourdomain.p7b{*}{color}{color:#333333}{*}{color}{color:#333333}With my.kdb being your keystore.{color}\\  {color:#333333}&amp;nbsp;{color}\\  {color:#333333}{*}Update server.xml configuration{color} {color:#333333}[file:\*|file:*]{color}\\  {color:#333333}1. Open "$JAKARTA_HOME/conf/server.xml" in a text editor.{color}\\  {color:#333333}2. Find the following section:{color}\\  {color:#333333}&lt;Connector{color}{color:#333333}&amp;nbsp;{color}\\  {color:#333333}...{color}{color:#333333}&amp;nbsp;{color}\\  {color:#333333}scheme="https"{color}{color:#333333}&amp;nbsp;{color}\\  {color:#333333}secure="true"{color}{color:#333333}&amp;nbsp;{color}\\  {color:#333333}keystoreFile="/pathto/my.kdb"{color}{color:#333333}&amp;nbsp;{color}\\  {color:#333333}keystorePass="mypassword"{color}\\  {color:#333333}3. If you want Tomcat to use the default SSL port, change all instances of the port number 8443 to 443.{color}\\  {color:#333333}4. Add the keystoreFile and keystorePass directives to correspond with the keystore file and password that you are using.{color}\\  {color:#333333}5. Start or restart Tomcat using the appropriate startup script (startup.sh for unix/linux or startup.bat for windows){color} | |</property>
    

<property name="body">Since the Ecommerce subnet is very locked down, we have to take a couple of extra steps to enable hosts to talk to each other even though they are in the same subnet.

For Ubuntu Server:

edit the /etc/rc.local file, and put the following lines at the bottom:

For the host you want to connect TO:


exec arp \-s &lt;ipaddress&gt;&lt;space&gt;&lt;macaddress&gt;

For the host you are ON: (optional; I like this for documentation purposes)


exec arp \-s &lt;ipaddress&lt;space&gt;&lt;macaddress&gt;

Save the file, and then make sure it is flagged executable.

That's it - on next reboot, you should be able to communicate with the remote box.</property>
    

<property name="body">Command to remove iptables from Red Hat linux boxes:
\\

&amp;nbsp;rpm \-e iptables iptables-ipv6 iptstate system-config-securitylevel system-config-securitylevel-tui firstboot system-config-keyboard firstboot-tui system-config-boot</property>
    

<property name="body">h2. First Step


h5. If IP is assigned by DHCP, make sure /etc/hosts file looks like this:
{code:title=/etc/hosts|borderStyle=solid}127.0.0.1     servername.suu.edu     localhost.localdomain     localhost     servername
{code}
h5. If IP is hard-coded, make sure /etc/hosts file looks like this (x.x is your new IP):
{code:title=/etc/hosts|borderStyle=solid}127.0.0.1     localhost.localdomain     localhost
134.250.x.x   yourserver.suu.edu        yourserver
{code}
h2. Second Step


h5. If you need the change to happen immediately without a reboot, run the following command as root:
{code:borderStyle=solid}#hostname yourserver.suu.edu
{code}
h2. Third Step


h5. This step is optional, and depends on the linux distribution and version you are using.  If you have an /etc/HOSTNAME file, ensure that it is populated with a single line as follows:
{code:borderStyle=solid}yourserver.suu.edu
{code}
h2. Fourth Step


h5. Edit the /etc/sysconfig/network file HOSTNAME line to read:
{code:title=/etc/sysconfig/network|borderStyle=solid}HOSTNAME=yourserver.suu.edu
{code}
h2. Fifth Step


h5. As root, run the following command:
{code:borderStyle=solid}#echo yourserver.suu.edu &gt; /proc/sys/kernel/hostname

To verify that it worked, run:
#cat /proc/sys/kernel/hostname
{code}
h2. Sixth Step
h5. Edit the /etc/sysconfig/network-scripts/ifcfg-eth0 file
h2. Finally, reboot.</property>
    

<property name="body">h1. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Example contents of dsm.sys file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMmethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu

nodename &lt;servernodename_goeshere&gt; ex. ASPEN
passwordaccess generate
MANAGEDSERVICES	schedule webclient

exclude core
exclude /.../core
exclude /.../tmp/.../*
exclude *_log
exclude *.log
exclude /tmp/*/.../*
exclude /mnt/*/.../*
exclude /.../Cache/*/.../*
exclude /var/run/*/.../*
exclude /var/tmp/*/.../*
exclude /proc/*/.../*
exclude /u0?/oradata/*/.../*
exclude /backup/*/.../*
exclude.dir /proc
exclude.dir /proc/
exclude.dir /dev
exclude.dir /dev/
exclude.dir /mnt
exclude.dir /mnt/
exclude.dir /usr/share/man
exclude dsmsched.log
exclude.dir /var/spool/cups/
exclude.dir /u01/app/sct/suupics
exclude.dir /u01/app/sct/suupics-www
exclude /u01/app/sct/suupics/*
exclude /u01/app/sct/suupics-www/*
{code}

h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
FOR UBUNTU SERVER:

chmod 755 suu_tivoli
update-rc.d suu_tivoli defaults

FOR RED HAT:
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc
It will prompt you for your nodename and password.  Once you have entered them, it will drop you at a tsm&gt; prompt.
You can then type 'backup', no quotes, and it will start an incremental backup.  If you don't want to start one right away,
just type 'quit', no quotes, and it will drop you back at the linux prompt.
To start the daemon, run the following command:

#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Server Notes

{code}
Installing TSM Client V5.5.2 on Ubuntu 9.04 Server 64-bit

Note: These instructions are based on the report "TSM-Client unter Debian/etch einrichten" at "https://wiki.gw.dg.de/index.php/TSM:debian"



1) get the latest client - modify version numbers as needed
wget "ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v5r5/Linux/LinuxX86/v552/5.5.2.0-TIV-TSMBAC-LinuxX86.tar"

** NOTE - execute "sudo su -" prior to running the following build and install.  Otherwise, permissions get jacked

2) apt-get install alien ksh libstdc++5 ia32-libs

3) unpack the archive
tar xvf 5.5.2.0-TIV-TSMBAC-LinuxX86.tar

4) unpack the RPM archives (ignore warnings re scripts)
alien -g TIVsm-API.i386.rpm
alien -g TIVsm-BA.i386.rpm

5) change directory names
mv TIVsm-API-5.5.1/debian TIVsm-API-5.5.2/DEBIAN
mv TIVsm-BA-5.5.1/debian TIVsm-BA-5.5.2/DEBIAN

6) edit the control files

vi TIVsm-API-5.5.2/DEBIAN/control
Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-api
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-api
Architecture: amd64
Depends:
Description: the API IBM Tivoli Storage Manager API
Version: 5.5.2
&lt;blank line&gt;

Save and exit the file.

vi TIVsm-BA-5.5.2/DEBIAN/control

Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-ba
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-ba
Architecture: amd64
Depends:
Description: the Backup Archive Client IBM Tivoli Storage Manager Client
Version: 5.5.2
&lt;blank line&gt;

Save and exit the file

7) create *.deb packages
dpkg -b TIVsm-API-5.5.2
dpkg -b TIVsm-BA-5.5.2

8) install *.deb packages
dpkg -i TIVsm-API-5.5.2.deb
dpkg -i TIVsm-BA-5.5.2.deb

9) create/modify TSM configuration files
 (use examples listed above)
vi /opt/tivoli/tsm/client/ba/bin/dsm.opt
vi /opt/tivoli/tsm/client/ba/bin/dsm.sys

10) Run the "Error loading shared libraries" fix located above; run the "English message repository not found" fix as well

11) run an incremental backup
dsmc incremental

12) start the TSM scheduler
start dsm-sched
{code}</property>
    

<property name="body">h1. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Example contents of dsm.sys file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMmethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu

nodename &lt;servernodename_goeshere&gt; ex. ASPEN
passwordaccess generate
MANAGEDSERVICES	schedule webclient

exclude core
exclude /.../core
exclude /.../tmp/.../*
exclude *_log
exclude *.log
exclude /tmp/*/.../*
exclude /mnt/*/.../*
exclude /.../Cache/*/.../*
exclude /var/run/*/.../*
exclude /var/tmp/*/.../*
exclude /proc/*/.../*
exclude /u0?/oradata/*/.../*
exclude /backup/*/.../*
exclude.dir /proc
exclude.dir /proc/
exclude.dir /dev
exclude.dir /dev/
exclude.dir /mnt
exclude.dir /mnt/
exclude.dir /usr/share/man
exclude dsmsched.log
exclude.dir /var/spool/cups/
exclude.dir /u01/app/sct/suupics
exclude.dir /u01/app/sct/suupics-www
exclude /u01/app/sct/suupics/*
exclude /u01/app/sct/suupics-www/*
{code}

h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
FOR UBUNTU SERVER:

chmod 755 suu_tivoli
update-rc.d suu_tivoli defaults

FOR RED HAT:
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc
It will prompt you for your nodename and password.  Once you have entered them, it will drop you at a tsm&gt; prompt.
You can then type 'backup', no quotes, and it will start an incremental backup.  If you don't want to start one right away,
just type 'quit', no quotes, and it will drop you back at the linux prompt.
To start the daemon, run the following command:

#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Server Notes

{code}
Installing TSM Client V5.5.2 on Ubuntu 9.04 Server 64-bit

Note: These instructions are based on the report "TSM-Client unter Debian/etch einrichten" at "https://wiki.gw.dg.de/index.php/TSM:debian"



1) get the latest client - modify version numbers as needed
wget "ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v5r5/Linux/LinuxX86/v552/5.5.2.0-TIV-TSMBAC-LinuxX86.tar"

** NOTE - execute "sudo su -" prior to running the following build and install.  Otherwise, permissions get jacked

2) apt-get install alien ksh libstdc++5 ia32-libs

3) unpack the archive
tar xvf 5.5.2.0-TIV-TSMBAC-LinuxX86.tar

4) unpack the RPM archives (ignore warnings re scripts)
alien -g TIVsm-API.i386.rpm
alien -g TIVsm-BA.i386.rpm

5) change directory names
mv TIVsm-API-5.5.1/debian TIVsm-API-5.5.2/DEBIAN
mv TIVsm-BA-5.5.1/debian TIVsm-BA-5.5.2/DEBIAN

6) edit the control files

vi TIVsm-API-5.5.2/DEBIAN/control
Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-api
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-api
Architecture: amd64
Depends:
Description: the API IBM Tivoli Storage Manager API
Version: 5.5.2
&lt;blank line&gt;

Save and exit the file.

vi TIVsm-BA-5.5.2/DEBIAN/control

Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-ba
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-ba
Architecture: amd64
Depends:
Description: the Backup Archive Client IBM Tivoli Storage Manager Client
Version: 5.5.2
&lt;blank line&gt;

Save and exit the file

7) create *.deb packages
dpkg -b TIVsm-API-5.5.2
dpkg -b TIVsm-BA-5.5.2

8) install *.deb packages
dpkg -i TIVsm-API-5.5.2.deb
dpkg -i TIVsm-BA-5.5.2.deb

9) create/modify TSM configuration files
 (use examples listed above)
vi /opt/tivoli/tsm/client/ba/bin/dsm.opt
vi /opt/tivoli/tsm/client/ba/bin/dsm.sys

10) Run the "Error loading shared libraries" fix located above; run the "English message repository not found" fix as well

11) Link the necessary libraries:
ln -s /opt/tivoli/tsm/client/api/bin/libgpfs.so
ln -s /opt/tivoli/tsm/client/api/bin/libdmapi.so
ln -s /opt/tivoli/tsm/client/api/bin/libha_gs_r.so
ln -s /opt/tivoli/tsm/client/api/bin/libxerces-c1_6_0.so
ln -s /opt/tivoli/tsm/client/api/bin/libxmlutil-5.5.2.0.so

11) run an incremental backup
dsmc incremental

12) start the TSM scheduler
start dsm-sched
{code}</property>
    

<property name="body">h1. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Example contents of dsm.sys file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMmethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu

nodename &lt;servernodename_goeshere&gt; ex. ASPEN
passwordaccess generate
MANAGEDSERVICES	schedule webclient

exclude core
exclude /.../core
exclude /.../tmp/.../*
exclude *_log
exclude *.log
exclude /tmp/*/.../*
exclude /mnt/*/.../*
exclude /.../Cache/*/.../*
exclude /var/run/*/.../*
exclude /var/tmp/*/.../*
exclude /proc/*/.../*
exclude /u0?/oradata/*/.../*
exclude /backup/*/.../*
exclude.dir /proc
exclude.dir /proc/
exclude.dir /dev
exclude.dir /dev/
exclude.dir /mnt
exclude.dir /mnt/
exclude.dir /usr/share/man
exclude dsmsched.log
exclude.dir /var/spool/cups/
exclude.dir /u01/app/sct/suupics
exclude.dir /u01/app/sct/suupics-www
exclude /u01/app/sct/suupics/*
exclude /u01/app/sct/suupics-www/*
{code}

h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
FOR UBUNTU SERVER:

chmod 755 suu_tivoli
update-rc.d suu_tivoli defaults

FOR RED HAT:
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc
It will prompt you for your nodename and password.  Once you have entered them, it will drop you at a tsm&gt; prompt.
You can then type 'backup', no quotes, and it will start an incremental backup.  If you don't want to start one right away,
just type 'quit', no quotes, and it will drop you back at the linux prompt.
To start the daemon, run the following command:

#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Server Notes

{code}
Installing TSM Client V5.5.2 on Ubuntu 9.04 Server 64-bit

Note: These instructions are based on the report "TSM-Client unter Debian/etch einrichten" at "https://wiki.gw.dg.de/index.php/TSM:debian"



1) get the latest client - modify version numbers as needed
wget "ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v5r5/Linux/LinuxX86/v552/5.5.2.0-TIV-TSMBAC-LinuxX86.tar"

** NOTE - execute "sudo su -" prior to running the following build and install.  Otherwise, permissions get jacked

2) apt-get install alien ksh libstdc++5 ia32-libs

3) unpack the archive
tar xvf 5.5.2.0-TIV-TSMBAC-LinuxX86.tar

4) unpack the RPM archives (ignore warnings re scripts)
alien -g TIVsm-API.i386.rpm
alien -g TIVsm-BA.i386.rpm

5) change directory names
mv TIVsm-API-5.5.1/debian TIVsm-API-5.5.2/DEBIAN
mv TIVsm-BA-5.5.1/debian TIVsm-BA-5.5.2/DEBIAN

6) edit the control files

vi TIVsm-API-5.5.2/DEBIAN/control
Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-api
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-api
Architecture: amd64
Depends:
Description: the API IBM Tivoli Storage Manager API
Version: 5.5.2
&lt;blank line&gt;

Save and exit the file.

vi TIVsm-BA-5.5.2/DEBIAN/control

Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-ba
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-ba
Architecture: amd64
Depends:
Description: the Backup Archive Client IBM Tivoli Storage Manager Client
Version: 5.5.2
&lt;blank line&gt;

Save and exit the file

7) create *.deb packages
dpkg -b TIVsm-API-5.5.2
dpkg -b TIVsm-BA-5.5.2

8) install *.deb packages
dpkg -i TIVsm-API-5.5.2.deb
dpkg -i TIVsm-BA-5.5.2.deb

9) create/modify TSM configuration files
 (use examples listed above)
vi /opt/tivoli/tsm/client/ba/bin/dsm.opt
vi /opt/tivoli/tsm/client/ba/bin/dsm.sys

10) Run the "Error loading shared libraries" fix located above; run the "English message repository not found" fix as well

11) Link the necessary libraries:
cd /usr/lib
ln -s /opt/tivoli/tsm/client/api/bin/libgpfs.so
ln -s /opt/tivoli/tsm/client/api/bin/libdmapi.so
ln -s /opt/tivoli/tsm/client/api/bin/libha_gs_r.so
ln -s /opt/tivoli/tsm/client/api/bin/libxerces-c1_6_0.so
ln -s /opt/tivoli/tsm/client/api/bin/libxmlutil-5.5.2.0.so

11) run an incremental backup
dsmc incremental

12) start the TSM scheduler
start dsm-sched
{code}</property>
    

<property name="body">h1. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Example contents of dsm.sys file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMmethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu

nodename &lt;servernodename_goeshere&gt; ex. ASPEN
passwordaccess generate
MANAGEDSERVICES	schedule webclient

exclude core
exclude /.../core
exclude /.../tmp/.../*
exclude *_log
exclude *.log
exclude /tmp/*/.../*
exclude /mnt/*/.../*
exclude /.../Cache/*/.../*
exclude /var/run/*/.../*
exclude /var/tmp/*/.../*
exclude /proc/*/.../*
exclude /u0?/oradata/*/.../*
exclude /backup/*/.../*
exclude.dir /proc
exclude.dir /proc/
exclude.dir /dev
exclude.dir /dev/
exclude.dir /mnt
exclude.dir /mnt/
exclude.dir /usr/share/man
exclude dsmsched.log
exclude.dir /var/spool/cups/
exclude.dir /u01/app/sct/suupics
exclude.dir /u01/app/sct/suupics-www
exclude /u01/app/sct/suupics/*
exclude /u01/app/sct/suupics-www/*
{code}

h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
FOR UBUNTU SERVER:

chmod 755 suu_tivoli
update-rc.d suu_tivoli defaults

FOR RED HAT:
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc
It will prompt you for your nodename and password.  Once you have entered them, it will drop you at a tsm&gt; prompt.
You can then type 'backup', no quotes, and it will start an incremental backup.  If you don't want to start one right away,
just type 'quit', no quotes, and it will drop you back at the linux prompt.
To start the daemon, run the following command:

#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Server Notes

{code}
Installing TSM Client V5.5.2 on Ubuntu 9.04 Server 64-bit

Note: These instructions are based on the report "TSM-Client unter Debian/etch einrichten" at "https://wiki.gw.dg.de/index.php/TSM:debian"



1) get the latest client - modify version numbers as needed
wget "ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v5r5/Linux/LinuxX86/v552/5.5.2.0-TIV-TSMBAC-LinuxX86.tar"

** NOTE - execute "sudo su -" prior to running the following build and install.  Otherwise, permissions get jacked

2) apt-get install alien ksh libstdc++5 ia32-libs

3) unpack the archive
tar xvf 5.5.2.0-TIV-TSMBAC-LinuxX86.tar

4) unpack the RPM archives (ignore warnings re scripts)
alien -g TIVsm-API.i386.rpm
alien -g TIVsm-BA.i386.rpm

5) change directory names
mv TIVsm-API-5.5.1/debian TIVsm-API-5.5.2/DEBIAN
mv TIVsm-BA-5.5.1/debian TIVsm-BA-5.5.2/DEBIAN

6) edit the control files

vi TIVsm-API-5.5.2/DEBIAN/control
Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-api
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-api
Architecture: amd64
Depends:
Description: the API IBM Tivoli Storage Manager API
Version: 5.5.2
&lt;blank line&gt;

Save and exit the file.

vi TIVsm-BA-5.5.2/DEBIAN/control

Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-ba
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-ba
Architecture: amd64
Depends:
Description: the Backup Archive Client IBM Tivoli Storage Manager Client
Version: 5.5.2
&lt;blank line&gt;

Save and exit the file

7) create *.deb packages
dpkg -b TIVsm-API-5.5.2
dpkg -b TIVsm-BA-5.5.2

8) install *.deb packages
dpkg -i TIVsm-API-5.5.2.deb
dpkg -i TIVsm-BA-5.5.2.deb

9) create/modify TSM configuration files
 (use examples listed above)
vi /opt/tivoli/tsm/client/ba/bin/dsm.opt
vi /opt/tivoli/tsm/client/ba/bin/dsm.sys

10) Run the "Error loading shared libraries" fix located above; run the "English message repository not found" fix as well

11) Link the necessary shared libraries:
add the dsm binary path on a line in the file /etc/ld.so.conf
/opt/tivoli/tsm/client/api/bin
import the shared objects using the command
ldconfig

11) run an incremental backup
dsmc incremental

12) start the TSM scheduler
start dsm-sched
{code}</property>
    

<property name="body">&lt;ac:structured-macro ac:macro-id="4a1e3248-714a-4683-b6ac-77694ed12762" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMMethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu
nodename MARKETPLACE
passwordaccess generate
MANAGEDSERVICES	schedule webclient
include /home/.../*
include /etc/.../*
exclude.dir /bin
exclude.dir /boot
exclude.dir /dev
exclude.dir /initrd
exclude.dir /lib
exclude.dir /lost*
exclude.dir /media
exclude.dir /mnt
exclude.dir /opt
exclude.dir /proc
exclude.dir /root
exclude.dir /sbin
exclude.dir /srv
exclude.dir /tmp
exclude.dir /usr/bin
exclude.dir /usr/games
exclude.dir /usr/include
exclude.dir /usr/lib
exclude.dir /usr/sbin
exclude.dir /usr/share
exclude.dir /usr/src
exclude.dir /usr/X11R6
exclude.dir /usr/local/bin
exclude.dir /usr/local/games
exclude.dir /usr/local/include
exclude.dir /usr/local/lib
exclude.dir /usr/local/sbin
exclude.dir /usr/local/share
exclude.dir /usr/local/src
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;</property>
    

<property name="body">{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMMethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu
nodename MARKETPLACE
passwordaccess generate
MANAGEDSERVICES	schedule webclient

include /usr/local/touchnet/.../*
include /home/.../*
exclude.dir /bin
exclude.dir /boot
exclude.dir /dev
exclude.dir /initrd
exclude.dir /lib
exclude.dir /lost*
exclude.dir /media
exclude.dir /mnt
exclude.dir /opt
exclude.dir /proc
exclude.dir /root
exclude.dir /sbin
exclude.dir /srv
exclude.dir /tmp
exclude.dir /var
exclude.dir /usr/bin
exclude.dir /usr/games
exclude.dir /usr/include
exclude.dir /usr/lib
exclude.dir /usr/sbin
exclude.dir /usr/share
exclude.dir /usr/src
exclude.dir /usr/X11R6
exclude.dir /usr/local/bin
exclude.dir /usr/local/etc
exclude.dir /usr/local/games
exclude.dir /usr/local/include
exclude.dir /usr/local/lib
exclude.dir /usr/local/sbin
exclude.dir /usr/local/share
exclude.dir /usr/local/src
{code}</property>
    

<property name="body">&lt;ac:structured-macro ac:macro-id="cdb5ad62-2db0-425d-b39c-0c8abeb0d22e" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
SErvername  tivoli
   COMMmethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu

nodename BIRCHINB 
passwordaccess generate
MANAGEDSERVICES	schedule webclient
include /u01/.../*
include /u02/.../*
include /u03/.../*
include /home/.../*
include /etc/.../*
include /root/.../*
exclude.dir /dev
exclude.dir /mnt
exclude.dir /opt
exclude.dir /proc
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;</property>
    

<property name="body">h1. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Example contents of dsm.sys file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMmethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu

nodename &lt;servernodename_goeshere&gt; ex. ASPEN
passwordaccess generate
MANAGEDSERVICES	schedule webclient

exclude core
exclude /.../core
exclude /.../tmp/.../*
exclude *_log
exclude *.log
exclude /tmp/*/.../*
exclude /mnt/*/.../*
exclude /.../Cache/*/.../*
exclude /var/run/*/.../*
exclude /var/tmp/*/.../*
exclude /proc/*/.../*
exclude /u0?/oradata/*/.../*
exclude /backup/*/.../*
exclude.dir /proc
exclude.dir /proc/
exclude.dir /dev
exclude.dir /dev/
exclude.dir /mnt
exclude.dir /mnt/
exclude.dir /usr/share/man
exclude dsmsched.log
exclude.dir /var/spool/cups/
exclude.dir /u01/app/sct/suupics
exclude.dir /u01/app/sct/suupics-www
exclude /u01/app/sct/suupics/*
exclude /u01/app/sct/suupics-www/*
{code}

h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
FOR UBUNTU SERVER:

chmod 755 suu_tivoli
update-rc.d suu_tivoli defaults

FOR RED HAT:
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc
It will prompt you for your nodename and password.  Once you have entered them, it will drop you at a tsm&gt; prompt.
You can then type 'backup', no quotes, and it will start an incremental backup.  If you don't want to start one right away,
just type 'quit', no quotes, and it will drop you back at the linux prompt.
To start the daemon, run the following command:

#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Server Notes

{code}
Installing TSM Client V5.5.2 on Ubuntu 9.04 Server 64-bit

Note: These instructions are based on the report "TSM-Client unter Debian/etch einrichten" at "https://wiki.gw.dg.de/index.php/TSM:debian"



1) get the latest client - modify version numbers as needed
wget "ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v5r5/Linux/LinuxX86/v552/5.5.2.0-TIV-TSMBAC-LinuxX86.tar"

** NOTE - execute "sudo su -" prior to running the following build and install.  Otherwise, permissions get jacked

2) apt-get install alien ksh libstdc++5 ia32-libs

3) unpack the archive
tar xvf 5.5.2.0-TIV-TSMBAC-LinuxX86.tar

4) unpack the RPM archives (ignore warnings re scripts)
alien -g TIVsm-API.i386.rpm
alien -g TIVsm-BA.i386.rpm

5) change directory names
mv TIVsm-API-5.5.1/debian TIVsm-API-5.5.2/DEBIAN
mv TIVsm-BA-5.5.1/debian TIVsm-BA-5.5.2/DEBIAN

6) edit the control files

vi TIVsm-API-5.5.2/DEBIAN/control
Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-api
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-api
Architecture: amd64
Depends:
Description: the API IBM Tivoli Storage Manager API
Version: 5.5.2
&lt;blank line&gt;

Save and exit the file.

vi TIVsm-BA-5.5.2/DEBIAN/control

Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-ba
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-ba
Architecture: amd64
Depends:
Description: the Backup Archive Client IBM Tivoli Storage Manager Client
Version: 5.5.2
&lt;blank line&gt;

Save and exit the file

7) create *.deb packages
dpkg -b TIVsm-API-5.5.2
dpkg -b TIVsm-BA-5.5.2

8) install *.deb packages
dpkg -i TIVsm-API-5.5.2.deb
dpkg -i TIVsm-BA-5.5.2.deb

9) create/modify TSM configuration files
 (use examples listed above)
vi /opt/tivoli/tsm/client/ba/bin/dsm.opt
vi /opt/tivoli/tsm/client/ba/bin/dsm.sys

10) Run the "Error loading shared libraries" fix located above; run the "English message repository not found" fix as well

11) Link the necessary shared libraries:
add the dsm binary path on a line in the file /etc/ld.so.conf
/opt/tivoli/tsm/client/api/bin
import the shared objects using the command
ldconfig

11) run an incremental backup
dsmc incremental

12) start the TSM scheduler
#/etc/init.d/suu_tivoli start
{code}</property>
    

<property name="body">h1. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
FOR UBUNTU SERVER:

chmod 755 suu_tivoli
update-rc.d suu_tivoli defaults

FOR RED HAT:
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc
It will prompt you for your nodename and password.  Once you have entered them, it will drop you at a tsm&gt; prompt.
You can then type 'backup', no quotes, and it will start an incremental backup.  If you don't want to start one right away,
just type 'quit', no quotes, and it will drop you back at the linux prompt.
To start the daemon, run the following command:

#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Server Notes

{code}
Installing TSM Client V5.5.2 on Ubuntu 9.04 Server 64-bit

Note: These instructions are based on the report "TSM-Client unter Debian/etch einrichten" at "https://wiki.gw.dg.de/index.php/TSM:debian"



1) get the latest client - modify version numbers as needed
wget "ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v5r5/Linux/LinuxX86/v552/5.5.2.0-TIV-TSMBAC-LinuxX86.tar"

** NOTE - execute "sudo su -" prior to running the following build and install.  Otherwise, permissions get jacked

2) apt-get install alien ksh libstdc++5 ia32-libs

3) unpack the archive
tar xvf 5.5.2.0-TIV-TSMBAC-LinuxX86.tar

4) unpack the RPM archives (ignore warnings re scripts)
alien -g TIVsm-API.i386.rpm
alien -g TIVsm-BA.i386.rpm

5) change directory names
mv TIVsm-API-5.5.1/debian TIVsm-API-5.5.2/DEBIAN
mv TIVsm-BA-5.5.1/debian TIVsm-BA-5.5.2/DEBIAN

6) edit the control files

vi TIVsm-API-5.5.2/DEBIAN/control
Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-api
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-api
Architecture: amd64
Depends:
Description: the API IBM Tivoli Storage Manager API
Version: 5.5.2
&lt;blank line&gt;

Save and exit the file.

vi TIVsm-BA-5.5.2/DEBIAN/control

Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-ba
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-ba
Architecture: amd64
Depends:
Description: the Backup Archive Client IBM Tivoli Storage Manager Client
Version: 5.5.2
&lt;blank line&gt;

Save and exit the file

7) create *.deb packages
dpkg -b TIVsm-API-5.5.2
dpkg -b TIVsm-BA-5.5.2

8) install *.deb packages
dpkg -i TIVsm-API-5.5.2.deb
dpkg -i TIVsm-BA-5.5.2.deb

9) create/modify TSM configuration files
 (use examples listed above)
vi /opt/tivoli/tsm/client/ba/bin/dsm.opt
vi /opt/tivoli/tsm/client/ba/bin/dsm.sys

10) Run the "Error loading shared libraries" fix located above; run the "English message repository not found" fix as well

11) Link the necessary shared libraries:
add the dsm binary path on a line in the file /etc/ld.so.conf
/opt/tivoli/tsm/client/api/bin
import the shared objects using the command
ldconfig

11) run an incremental backup
dsmc incremental

12) start the TSM scheduler
#/etc/init.d/suu_tivoli start
{code}</property>
    

<property name="body">h1. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
FOR UBUNTU SERVER:

chmod 755 suu_tivoli
update-rc.d suu_tivoli defaults

FOR RED HAT:
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc
It will prompt you for your nodename and password.  Once you have entered them, it will drop you at a tsm&gt; prompt.
You can then type 'backup', no quotes, and it will start an incremental backup.  If you don't want to start one right away,
just type 'quit', no quotes, and it will drop you back at the linux prompt.
To start the daemon, run the following command:

#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Server Notes

{code}
Installing TSM Client V5.5.2 on Ubuntu 9.04 Server 64-bit

Note: These instructions are based on the report "TSM-Client unter Debian/etch einrichten" at "https://wiki.gw.dg.de/index.php/TSM:debian"



1) get the latest client - modify version numbers as needed
wget "ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v5r5/Linux/LinuxX86/v552/5.5.2.0-TIV-TSMBAC-LinuxX86.tar"

** NOTE - execute "sudo su -" prior to running the following build and install.  Otherwise, permissions get jacked

2) apt-get install alien ksh ia32-libs

3) unpack the archive
tar xvf 5.5.2.0-TIV-TSMBAC-LinuxX86.tar

4) unpack the RPM archives (ignore warnings re scripts)
alien -g TIVsm-API.i386.rpm
alien -g TIVsm-BA.i386.rpm

5) change directory names
mv TIVsm-API-5.5.1/debian TIVsm-API-5.5.2/DEBIAN
mv TIVsm-BA-5.5.1/debian TIVsm-BA-5.5.2/DEBIAN

6) edit the control files

vi TIVsm-API-5.5.2/DEBIAN/control
Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-api
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-api
Architecture: amd64
Depends:
Description: the API IBM Tivoli Storage Manager API
Version: 5.5.2
&lt;blank line&gt;

Save and exit the file.

vi TIVsm-BA-5.5.2/DEBIAN/control

Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-ba
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-ba
Architecture: amd64
Depends:
Description: the Backup Archive Client IBM Tivoli Storage Manager Client
Version: 5.5.2
&lt;blank line&gt;

Save and exit the file

7) create *.deb packages
dpkg -b TIVsm-API-5.5.2
dpkg -b TIVsm-BA-5.5.2

8) install *.deb packages
dpkg -i TIVsm-API-5.5.2.deb
dpkg -i TIVsm-BA-5.5.2.deb

9) create/modify TSM configuration files
 (use examples listed above)
vi /opt/tivoli/tsm/client/ba/bin/dsm.opt
vi /opt/tivoli/tsm/client/ba/bin/dsm.sys

10) Run the "Error loading shared libraries" fix located above; run the "English message repository not found" fix as well

11) Link the necessary shared libraries:
add the dsm binary path on a line in the file /etc/ld.so.conf
/opt/tivoli/tsm/client/api/bin
import the shared objects using the command
ldconfig

11) run an incremental backup
dsmc incremental

12) start the TSM scheduler
#/etc/init.d/suu_tivoli start
{code}</property>
    

<property name="body">h1. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
FOR UBUNTU SERVER:

chmod 755 suu_tivoli
update-rc.d suu_tivoli defaults

FOR RED HAT:
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc
It will prompt you for your nodename and password.  Once you have entered them, it will drop you at a tsm&gt; prompt.
You can then type 'backup', no quotes, and it will start an incremental backup.  If you don't want to start one right away,
just type 'quit', no quotes, and it will drop you back at the linux prompt.
To start the daemon, run the following command:

#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Server Notes

{code}
Installing TSM Client V5.5.2 on Ubuntu 9.04 Server 64-bit

Note: These instructions are based on the report "TSM-Client unter Debian/etch einrichten" at "https://wiki.gw.dg.de/index.php/TSM:debian"



1) get the latest client - modify version numbers as needed
wget "ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v5r5/Linux/LinuxX86/v552/5.5.2.0-TIV-TSMBAC-LinuxX86.tar"

** NOTE - execute "sudo su -" prior to running the following build and install.  Otherwise, permissions get jacked

2) apt-get install alien ksh ia32-libs

3) unpack the archive
tar xvf 5.5.2.0-TIV-TSMBAC-LinuxX86.tar

4) unpack the RPM archives (ignore warnings re scripts)
alien -g TIVsm-API.i386.rpm
alien -g TIVsm-BA.i386.rpm

5) change directory names
mv TIVsm-API-5.5.1/debian TIVsm-API-5.5.2/DEBIAN
mv TIVsm-BA-5.5.1/debian TIVsm-BA-5.5.2/DEBIAN

6) edit the control files

vi TIVsm-API-5.5.2/DEBIAN/control
Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-api
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-api
Architecture: amd64
Depends:
Description: the API IBM Tivoli Storage Manager API
Version: 5.5.2
&lt;blank line&gt;

Save and exit the file.

vi TIVsm-BA-5.5.2/DEBIAN/control

Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-ba
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-ba
Architecture: amd64
Depends:
Description: the Backup Archive Client IBM Tivoli Storage Manager Client
Version: 5.5.2
&lt;blank line&gt;

Save and exit the file

7) create *.deb packages
dpkg -b TIVsm-API-5.5.2
dpkg -b TIVsm-BA-5.5.2

8) install *.deb packages
dpkg -i TIVsm-API-5.5.2.deb
dpkg -i TIVsm-BA-5.5.2.deb

9)
{code}
cd /tmp
wget http://security.ubuntu.com/ubuntu/pool/universe/i/ia32-libs/ia32-libs_2.7ubuntu6.1_amd64.deb
dpkg-deb -x ia32-libs_2.7ubuntu6.1_amd64.deb ia32-libs
sudo cp ia32-libs/usr/lib32/libstdc++.so.5.0.7 /usr/lib32/
cd /usr/lib32
sudo ln -s libstdc++.so.5.0.7 libstdc++.so.5
{code}

11) create/modify TSM configuration files
 (use examples listed above)
vi /opt/tivoli/tsm/client/ba/bin/dsm.opt
vi /opt/tivoli/tsm/client/ba/bin/dsm.sys

12) Run the "Error loading shared libraries" fix located above; run the "English message repository not found" fix as well

13) Link the necessary shared libraries:
add the dsm binary path on a line in the file /etc/ld.so.conf
/opt/tivoli/tsm/client/api/bin
import the shared objects using the command
ldconfig

14) run an incremental backup
dsmc incremental

15) start the TSM scheduler
#/etc/init.d/suu_tivoli start
{code}</property>
    

<property name="body">h1. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
FOR UBUNTU SERVER:

chmod 755 suu_tivoli
update-rc.d suu_tivoli defaults

FOR RED HAT:
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc
It will prompt you for your nodename and password.  Once you have entered them, it will drop you at a tsm&gt; prompt.
You can then type 'backup', no quotes, and it will start an incremental backup.  If you don't want to start one right away,
just type 'quit', no quotes, and it will drop you back at the linux prompt.
To start the daemon, run the following command:

#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Server Notes

{code}
Installing TSM Client V5.5.2 on Ubuntu 9.04 Server 64-bit

Note: These instructions are based on the report "TSM-Client unter Debian/etch einrichten" at "https://wiki.gw.dg.de/index.php/TSM:debian"



1) get the latest client - modify version numbers as needed
wget "ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v5r5/Linux/LinuxX86/v552/5.5.2.0-TIV-TSMBAC-LinuxX86.tar"

** NOTE - execute "sudo su -" prior to running the following build and install.  Otherwise, permissions get jacked

2) apt-get install alien ksh ia32-libs

3) unpack the archive
tar xvf 5.5.2.0-TIV-TSMBAC-LinuxX86.tar

4) unpack the RPM archives (ignore warnings re scripts)
alien -g TIVsm-API.i386.rpm
alien -g TIVsm-BA.i386.rpm

5) change directory names
mv TIVsm-API-5.5.1/debian TIVsm-API-5.5.2/DEBIAN
mv TIVsm-BA-5.5.1/debian TIVsm-BA-5.5.2/DEBIAN

6) edit the control files

vi TIVsm-API-5.5.2/DEBIAN/control
Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-api
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-api
Architecture: amd64
Depends:
Description: the API IBM Tivoli Storage Manager API
Version: 5.5.2
&lt;blank line&gt;

Save and exit the file.

vi TIVsm-BA-5.5.2/DEBIAN/control

Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-ba
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-ba
Architecture: amd64
Depends:
Description: the Backup Archive Client IBM Tivoli Storage Manager Client
Version: 5.5.2
&lt;blank line&gt;

Save and exit the file

7) create *.deb packages
dpkg -b TIVsm-API-5.5.2
dpkg -b TIVsm-BA-5.5.2

8) install *.deb packages
dpkg -i TIVsm-API-5.5.2.deb
dpkg -i TIVsm-BA-5.5.2.deb

9)
cd /tmp
wget [http://security.ubuntu.com/ubuntu/pool/universe/i/ia32-libs/ia32-libs_2.7ubuntu6.1_amd64.deb]
dpkg-deb \-x ia32-libs_2.7ubuntu6.1_amd64.deb ia32-libs
sudo cp ia32-libs/usr/lib32/libstdc++.so.5.0.7 /usr/lib32/
cd /usr/lib32
sudo ln \-s libstdc\++.so.5.0.7 libstdc+\+.so.5
10) create/modify TSM configuration files
 (use examples listed above)
vi /opt/tivoli/tsm/client/ba/bin/dsm.opt
vi /opt/tivoli/tsm/client/ba/bin/dsm.sys

11) Run the "Error loading shared libraries" fix located above; run the "English message repository not found" fix as well

12) Link the necessary shared libraries:
add the dsm binary path on a line in the file /etc/ld.so.conf
/opt/tivoli/tsm/client/api/bin
import the shared objects using the command
ldconfig

13) run an incremental backup
dsmc incremental

14) start the TSM scheduler
#/etc/init.d/suu_tivoli start
{code}</property>
    

<property name="body">&lt;p&gt;1. Download the client zip file from sherpa or the Oracle site&lt;/p&gt;

&lt;p&gt;2. Install the following additional packages:&lt;/p&gt;
&lt;ac:structured-macro ac:macro-id="5c4bdbec-c523-46d2-a19f-04d1e8ee6bec" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
#apt-get install libaio1 gawk
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;
&lt;p&gt;Additionally, be sure you are running the sun java software, not the default packaged version with Ubuntu.  You will also make a link for awk to gawk.&lt;/p&gt;
&lt;ac:structured-macro ac:macro-id="4a447483-e9c7-4e23-bb14-ae694a8e6dd5" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
#apt-get install sun-java6-bin sun-java6-jre sun-java6-plugin sun-java6-jdk
#cd /etc/alternatives
#ln -s /usr/lib/jvm/java-6-sun/jre/bin/java java
#cd /usr/bin
#ln -s /usr/bin/gawk awk
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;

&lt;p&gt;3. Next, we will initiate the installer to see where it fails and what settings we need to add to our /etc/sysctl.conf file.  Initiate the installer as follows, and then CANCEL as soon as you have the values you need:&lt;/p&gt;
&lt;ac:structured-macro ac:macro-id="c57db474-245b-4c1c-a785-42caeb2e62bb" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
./runinstaller -ignoreSysPrereqs
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;
&lt;p&gt;You will reach a point where it checks for needed settings, and gives you a list of everything that does not meet requirements.  The settings you are interested in are listed in the next step.  Make a note of the values the installer recommends.&lt;/p&gt;

&lt;p&gt;4. Add the following entries to your /etc/sysctl.conf file: (change values to match what is recommended for your machine - some will be the same, some won't)&lt;/p&gt;
&lt;ac:structured-macro ac:macro-id="52d5844b-5c6b-48df-b687-fe32e6851f92" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
# Oracle client stuff
kernel.shmmax = 536870912
kernel.sem = 250 32000 100 128
net.ipv4.ip_local_port_range = 9000 65500
net.core.rmem_default = 4194304
net.core.rmem_max = 4194304
net.core.wmem_default = 262144
net.core.wmem_max = 262144
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;
&lt;p&gt;Next, run the following to make the settings active:&lt;/p&gt;
&lt;ac:structured-macro ac:macro-id="e72e1f50-6e0a-4d2b-bf33-e23d15d22238" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
#sysctl -p
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;

&lt;p&gt;5. Now you can run the installer and ignore the warnings completely (there is a checkbox to do this)&lt;/p&gt;
&lt;ac:structured-macro ac:macro-id="21b82212-8dbd-4647-9e31-205bf8c43252" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
./runinstaller -ignoreSysPrereqs
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;

&lt;p&gt;6. Once it is finished, make a note of where you installed it to, and make the following entries in your .bashrc file:&lt;/p&gt;

&lt;ac:structured-macro ac:macro-id="4431977c-410d-4fae-ab66-eaa892747fdb" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
#Oracle stuff
export ORACLE_HOME=/&lt;path_to_where_you_installed&gt;/product/11.2.0/client_1
export PATH=$PATH:$ORACLE_HOME/bin
export TNS_ADMIN=$ORACLE_HOME/network/admin
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;
&lt;p&gt;Next, run the following to make it active (NOT as root - run as your user):&lt;/p&gt;
&lt;ac:structured-macro ac:macro-id="0fe07fc2-7695-4dc3-800c-7e9d1ede51f6" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
$ . .bashrc
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;
&lt;p&gt;If that is difficult to read, it is:&lt;/p&gt;
&lt;ac:structured-macro ac:macro-id="d73a3fd7-141d-4ff6-b703-04b7d445cfab" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
&lt;dot&gt;&lt;space&gt;&lt;dot&gt;&lt;bashrc&gt;
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;

&lt;p&gt;7. Lastly, copy the contents of a known good tnsnames.ora file, and paste it into the following file:&lt;/p&gt;
&lt;ac:structured-macro ac:macro-id="b4e82fec-06f4-4b2c-873c-ad440a9e3936" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
$ORACLE_HOME/network/admin/tnsnames.ora
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;

&lt;p&gt;8. Run tnsping against any of the tnsnames entries, and make sure you get a response.&lt;/p&gt;</property>
    

<property name="body">1. Download the client zip file from sherpa or the Oracle site

2. Install the following additional packages:
{code}
#apt-get install libaio1 gawk
{code}
Additionally, be sure you are running the sun java software, not the default packaged version with Ubuntu.
{code}
#apt-get install sun-java6-bin sun-java6-jre sun-java6-plugin sun-java6-jdk
#cd /etc/alternatives
#ln -s /usr/lib/jvm/java-6-sun/jre/bin/java java
#cd /usr/bin
#ln -s /usr/bin/gawk awk
{code}

3. Next, we will initiate the installer to see where it fails and what settings we need to add to our /etc/sysctl.conf file.  Initiate the installer as follows, and then CANCEL as soon as you have the values you need:
{code}
./runinstaller -ignoreSysPrereqs
{code}
You will reach a point where it checks for needed settings, and gives you a list of everything that does not meet requirements.  The settings you are interested in are listed in the next step.  Make a note of the values the installer recommends.

3. Add the following entries to your /etc/sysctl.conf file: (change values to match what is recommended for your machine - some will be the same, some won't)
{code}
# Oracle client stuff
kernel.shmmax = 536870912
kernel.sem = 250 32000 100 128
net.ipv4.ip_local_port_range = 9000 65500
net.core.rmem_default = 4194304
net.core.rmem_max = 4194304
net.core.wmem_default = 262144
net.core.wmem_max = 262144
{code}
Next, run the following to make the settings active:
{code}
#sysctl -p
{code}

2. Unzip and run the installer as follows:
{code}
./runinstaller -ignoreSysPrereqs
{code}</property>
    

<property name="body">1. Download the client zip file from sherpa or the Oracle site

2. Install the following additional packages:
{code}
#apt-get install libaio1 gawk
{code}
Additionally, be sure you are running the sun java software, not the default packaged version with Ubuntu.  You will also make a link for awk to gawk.
{code}
#apt-get install sun-java6-bin sun-java6-jre sun-java6-plugin sun-java6-jdk
#cd /etc/alternatives
#ln -s /usr/lib/jvm/java-6-sun/jre/bin/java java
#cd /usr/bin
#ln -s /usr/bin/gawk awk
{code}

3. Next, we will initiate the installer to see where it fails and what settings we need to add to our /etc/sysctl.conf file.  Initiate the installer as follows, and then CANCEL as soon as you have the values you need:
{code}
./runinstaller -ignoreSysPrereqs
{code}
You will reach a point where it checks for needed settings, and gives you a list of everything that does not meet requirements.  The settings you are interested in are listed in the next step.  Make a note of the values the installer recommends.

4. Add the following entries to your /etc/sysctl.conf file: (change values to match what is recommended for your machine - some will be the same, some won't)
{code}
# Oracle client stuff
kernel.shmmax = 536870912
kernel.sem = 250 32000 100 128
net.ipv4.ip_local_port_range = 9000 65500
net.core.rmem_default = 4194304
net.core.rmem_max = 4194304
net.core.wmem_default = 262144
net.core.wmem_max = 262144
{code}
Next, run the following to make the settings active:
{code}
#sysctl -p
{code}

5. Now you can run the installer and ignore the warnings completely (there is a checkbox to do this)
{code}
./runinstaller -ignoreSysPrereqs
{code}

6. Once it is finished, make a note of where you installed it to, and make the following entries in your .bashrc file:

{code}
#Oracle stuff
export ORACLE_HOME=/&lt;path_to_where_you_installed&gt;/product/11.2.0/client_1
export PATH=$PATH:$ORACLE_HOME/bin
{code}
Next, run the following to make it active (NOT as root - run as your user):
{code}
$ . .bashrc
{code}
If that is difficult to read, it is:
&lt;dot&gt;&lt;space&gt;&lt;dot&gt;&lt;bashrc&gt;
{code}</property>
    

<property name="body">1. Download the client zip file from sherpa or the Oracle site

2. Install the following additional packages:
{code}
#apt-get install libaio1 gawk
{code}
Additionally, be sure you are running the sun java software, not the default packaged version with Ubuntu.  You will also make a link for awk to gawk.
{code}
#apt-get install sun-java6-bin sun-java6-jre sun-java6-plugin sun-java6-jdk
#cd /etc/alternatives
#ln -s /usr/lib/jvm/java-6-sun/jre/bin/java java
#cd /usr/bin
#ln -s /usr/bin/gawk awk
{code}

3. Next, we will initiate the installer to see where it fails and what settings we need to add to our /etc/sysctl.conf file.  Initiate the installer as follows, and then CANCEL as soon as you have the values you need:
{code}
./runinstaller -ignoreSysPrereqs
{code}
You will reach a point where it checks for needed settings, and gives you a list of everything that does not meet requirements.  The settings you are interested in are listed in the next step.  Make a note of the values the installer recommends.

4. Add the following entries to your /etc/sysctl.conf file: (change values to match what is recommended for your machine - some will be the same, some won't)
{code}
# Oracle client stuff
kernel.shmmax = 536870912
kernel.sem = 250 32000 100 128
net.ipv4.ip_local_port_range = 9000 65500
net.core.rmem_default = 4194304
net.core.rmem_max = 4194304
net.core.wmem_default = 262144
net.core.wmem_max = 262144
{code}
Next, run the following to make the settings active:
{code}
#sysctl -p
{code}

5. Now you can run the installer and ignore the warnings completely (there is a checkbox to do this)
{code}
./runinstaller -ignoreSysPrereqs
{code}

6. Once it is finished, make a note of where you installed it to, and make the following entries in your .bashrc file:

{code}
#Oracle stuff
export ORACLE_HOME=/&lt;path_to_where_you_installed&gt;/product/11.2.0/client_1
export PATH=$PATH:$ORACLE_HOME/bin
{code}
Next, run the following to make it active (NOT as root - run as your user):
{code}
{code}
$ . .bashrc
{code}
If that is difficult to read, it is:
{code}
&lt;dot&gt;&lt;space&gt;&lt;dot&gt;&lt;bashrc&gt;
{code}</property>
    

<property name="body">1. Download the client zip file from sherpa or the Oracle site

2. Install the following additional packages:
{code}
#apt-get install libaio1 gawk
{code}
Additionally, be sure you are running the sun java software, not the default packaged version with Ubuntu.  You will also make a link for awk to gawk.
{code}
#apt-get install sun-java6-bin sun-java6-jre sun-java6-plugin sun-java6-jdk
#cd /etc/alternatives
#ln -s /usr/lib/jvm/java-6-sun/jre/bin/java java
#cd /usr/bin
#ln -s /usr/bin/gawk awk
{code}

3. Next, we will initiate the installer to see where it fails and what settings we need to add to our /etc/sysctl.conf file.  Initiate the installer as follows, and then CANCEL as soon as you have the values you need:
{code}
./runinstaller -ignoreSysPrereqs
{code}
You will reach a point where it checks for needed settings, and gives you a list of everything that does not meet requirements.  The settings you are interested in are listed in the next step.  Make a note of the values the installer recommends.

4. Add the following entries to your /etc/sysctl.conf file: (change values to match what is recommended for your machine - some will be the same, some won't)
{code}
# Oracle client stuff
kernel.shmmax = 536870912
kernel.sem = 250 32000 100 128
net.ipv4.ip_local_port_range = 9000 65500
net.core.rmem_default = 4194304
net.core.rmem_max = 4194304
net.core.wmem_default = 262144
net.core.wmem_max = 262144
{code}
Next, run the following to make the settings active:
{code}
#sysctl -p
{code}

5. Now you can run the installer and ignore the warnings completely (there is a checkbox to do this)
{code}
./runinstaller -ignoreSysPrereqs
{code}

6. Once it is finished, make a note of where you installed it to, and make the following entries in your .bashrc file:

{code}
#Oracle stuff
export ORACLE_HOME=/&lt;path_to_where_you_installed&gt;/product/11.2.0/client_1
export PATH=$PATH:$ORACLE_HOME/bin
{code}
Next, run the following to make it active (NOT as root - run as your user):
{code}
$ . .bashrc
{code}
If that is difficult to read, it is:
{code}
&lt;dot&gt;&lt;space&gt;&lt;dot&gt;&lt;bashrc&gt;
{code}</property>
    

<property name="body">1. Download the client zip file from sherpa or the Oracle site

2. Install the following additional packages:
{code}
#apt-get install libaio1 gawk
{code}
Additionally, be sure you are running the sun java software, not the default packaged version with Ubuntu.  You will also make a link for awk to gawk.
{code}
#apt-get install sun-java6-bin sun-java6-jre sun-java6-plugin sun-java6-jdk
#cd /etc/alternatives
#ln -s /usr/lib/jvm/java-6-sun/jre/bin/java java
#cd /usr/bin
#ln -s /usr/bin/gawk awk
{code}

3. Next, we will initiate the installer to see where it fails and what settings we need to add to our /etc/sysctl.conf file.  Initiate the installer as follows, and then CANCEL as soon as you have the values you need:
{code}
./runinstaller -ignoreSysPrereqs
{code}
You will reach a point where it checks for needed settings, and gives you a list of everything that does not meet requirements.  The settings you are interested in are listed in the next step.  Make a note of the values the installer recommends.

4. Add the following entries to your /etc/sysctl.conf file: (change values to match what is recommended for your machine - some will be the same, some won't)
{code}
# Oracle client stuff
kernel.shmmax = 536870912
kernel.sem = 250 32000 100 128
net.ipv4.ip_local_port_range = 9000 65500
net.core.rmem_default = 4194304
net.core.rmem_max = 4194304
net.core.wmem_default = 262144
net.core.wmem_max = 262144
{code}
Next, run the following to make the settings active:
{code}
#sysctl -p
{code}

5. Now you can run the installer and ignore the warnings completely (there is a checkbox to do this)
{code}
./runinstaller -ignoreSysPrereqs
{code}

6. Once it is finished, make a note of where you installed it to, and make the following entries in your .bashrc file:

{code}
#Oracle stuff
export ORACLE_HOME=/&lt;path_to_where_you_installed&gt;/product/11.2.0/client_1
export PATH=$PATH:$ORACLE_HOME/bin
{code}
Next, run the following to make it active (NOT as root - run as your user):
{code}
$ . .bashrc
{code}
If that is difficult to read, it is:
{code}
&lt;dot&gt;&lt;space&gt;&lt;dot&gt;&lt;bashrc&gt;
{code}

7. Lastly, copy the contents of a known good tnsnames.ora file, and paste it into the following file:
{code}
$ORACLE_HOME/network/admin/tnsnames.ora
{code}

8. Run tnsping against any of the tnsnames entries, and make sure you get a response.</property>
    

<property name="body">&lt;p&gt;1. Add the following line to the bottom of your /etc/apt/sources.list file:&lt;/p&gt;
&lt;ac:structured-macro ac:macro-id="64968a8c-633d-4c5c-a4b8-d5c68ddf3b58" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
deb http://download.virtualbox.org/virtualbox/debian] karmic non-free
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;
&lt;p&gt;2. Import the key:&lt;/p&gt;
&lt;ac:structured-macro ac:macro-id="c5504df9-bc65-41b1-a296-63dac6b977d4" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
sudo wget -q http://download.virtualbox.org/virtualbox/debian/sun_vbox.asc -O- | sudo apt-key add -
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;

&lt;p&gt;Refresh the repositories:&lt;/p&gt;
&lt;ac:structured-macro ac:macro-id="2f400169-ff3b-40e0-901e-075fff746655" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
sudo apt-get update
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;

&lt;p&gt;3. Install the latest virtualbox package (as of this writing it is virtualbox-3.1) by selecting it in Synaptic, or running this command from a terminal:&lt;/p&gt;
&lt;ac:structured-macro ac:macro-id="1722a9ac-f5ab-4824-b2c7-8a868b755c78" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
 $ sudo apt-get install virtualbox-3.1
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;
&lt;p&gt;4.  Add yourself to the vboxusers group:&lt;/p&gt;
&lt;ac:structured-macro ac:macro-id="387ecade-26cf-45ae-a030-810e563d8f18" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
 $ sudo gpasswd -a YOURUSERNAME vboxusers
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;
&lt;p&gt;5.  Find the devgid for the vboxusers group:&lt;/p&gt;
&lt;ac:structured-macro ac:macro-id="0c61c2ef-b72d-42fa-9e52-cbacef727075" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
 $ grep vboxusers /etc/group
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;
&lt;p&gt;It will return something like:&lt;/p&gt;
&lt;ac:structured-macro ac:macro-id="fd589180-ec16-4ae5-bd15-cfcdb3ddc52c" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
 vboxusers:x:121:username
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;
&lt;p&gt;Add this line to the bottom of /etc/fstab, replacing the devgid number with your devgid:&lt;/p&gt;
&lt;ac:structured-macro ac:macro-id="dc6aa3fa-af67-41d5-9fb5-9af50bd3c2ce" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
none /proc/bus/usb usbfs devgid=125,devmode=664 0 0
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;

&lt;p&gt;After you reboot you should now have USB support in VirtualBox.&lt;/p&gt;

&lt;p&gt;Last tested on Ubuntu 9.10 Karmic Koala&lt;/p&gt;</property>
    

<property name="body">1. Add the VirtualBox repo for Karmic. Click System &gt; Administration &gt; Software Sources. Click the ‘Third Party Software’ tab. Click ‘Add’ and enter:
 deb http://download.virtualbox.org/virtualbox/debian karmic non-free

2. Import the key:
{code}
sudo wget -q http://download.virtualbox.org/virtualbox/debian/sun_vbox.asc -O- | sudo apt-key add -
{code}

Click the ‘Reload’ button in Synaptic to reload the repositories, or run the following commands:
{code}
sudo apt-get update
{code}

3. Install the latest virtualbox package (as of this writing it is virtualbox-3.1) by selecting it in Synaptic, or running this command from a terminal:
{code}
 $ sudo apt-get install virtualbox-3.1
{code}
4.  Add yourself to the vboxusers group:
{code}
 $ sudo gpasswd -a YOURUSERNAME vboxusers
{code}
5.  Find the devgid for ‘vboxusers’:
{code}
 $ grep vboxusers /etc/group
{code}
It will return something like:
{code}
 vboxusers:x:121:username
{code}
Add this line to the bottom of /etc/fstab, replacing the devgid number with your devgid:
{code}
none /proc/bus/usb usbfs devgid=125,devmode=664 0 0
{code}

After you reboot you should now have USB support in VirtualBox.

Last tested on Ubuntu 9.10 Karmic Koala</property>
    

<property name="body">&lt;p&gt;Similar to Windows Software Update Services, apt-mirror allows us to store a local copy of the Ubuntu updates repository so our machines don't all have to go out to the internet for updates. &amp;nbsp;Not only does this reduce our bandwidth usage, but updates are delivered extremely quickly over local wire. &amp;nbsp;Here is an example of an /etc/apt/sources.list file from an Ubuntu 10.04 LTS 32-bit server install, pointed at our local repository on sherpa.suu.edu:&lt;/p&gt;

&lt;ac:structured-macro ac:macro-id="205f526b-6328-4a23-b218-240c9d744e72" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[

deb http://sherpa.suu.edu/ubuntu/ lucid main restricted

## Major bug fix updates produced after the final release of the
## distribution.
deb http://sherpa.suu.edu/ubuntu/ lucid-updates main restricted

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://sherpa.suu.edu/ubuntu/ lucid universe
deb http://sherpa.suu.edu/ubuntu/ lucid-updates universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu 
## team, and may not be under a free licence. Please satisfy yourself as to 
## your rights to use the software. Also, please note that software in 
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://sherpa.suu.edu/ubuntu/ lucid multiverse
deb http://sherpa.suu.edu/ubuntu/ lucid-updates multiverse

## Uncomment the following line to add software from Canonical's
## 'partner' repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
## respective vendors as a service to Ubuntu users.
deb http://sherpa.suu.edu/ubuntupartner lucid partner

## Security Updates
deb http://sherpa.suu.edu/updates lucid-security main restricted
deb http://sherpa.suu.edu/updates lucid-security universe
deb http://sherpa.suu.edu/updates lucid-security multiverse

]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;

&lt;p&gt;NOTE:  We do not currently mirror the deb-src (sources) files, since we rarely if ever compile our packages from source.  Adding these sources to every subsection listed here would more than double the required space to store them.  Your original sources.list file may or may not reference the source repositories.  If it does, you should remove the lines from your file, or at least comment them out.  If you need them, the only solution at this time is to leave them pointed at the original ubuntu location.&lt;/p&gt;


&lt;p&gt;For reference, here is a standard unmodified sources.list from an 11.10 box:&lt;/p&gt;
&lt;ac:structured-macro ac:macro-id="24186098-63ea-43e2-a430-55a9759eff08" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
deb http://us.archive.ubuntu.com/ubuntu/ oneiric main restricted
deb-src http://us.archive.ubuntu.com/ubuntu/ oneiric main restricted
deb http://us.archive.ubuntu.com/ubuntu/ oneiric-updates main restricted
deb-src http://us.archive.ubuntu.com/ubuntu/ oneiric-updates main restricted
deb http://us.archive.ubuntu.com/ubuntu/ oneiric universe
deb-src http://us.archive.ubuntu.com/ubuntu/ oneiric universe
deb http://us.archive.ubuntu.com/ubuntu/ oneiric-updates universe
deb-src http://us.archive.ubuntu.com/ubuntu/ oneiric-updates universe
deb http://us.archive.ubuntu.com/ubuntu/ oneiric multiverse
deb-src http://us.archive.ubuntu.com/ubuntu/ oneiric multiverse
deb http://us.archive.ubuntu.com/ubuntu/ oneiric-updates multiverse
deb-src http://us.archive.ubuntu.com/ubuntu/ oneiric-updates multiverse
# deb http://us.archive.ubuntu.com/ubuntu/ maverick-backports main restricted universe multiverse
# deb-src http://us.archive.ubuntu.com/ubuntu/ maverick-backports main restricted universe multiverse
deb http://archive.canonical.com/ubuntu oneiric partner
deb-src http://archive.canonical.com/ubuntu oneiric partner
deb http://extras.ubuntu.com/ubuntu oneiric main
deb-src http://extras.ubuntu.com/ubuntu oneiric main

deb http://security.ubuntu.com/ubuntu oneiric-security main restricted
deb-src http://security.ubuntu.com/ubuntu oneiric-security main restricted
deb http://security.ubuntu.com/ubuntu oneiric-security universe
deb-src http://security.ubuntu.com/ubuntu oneiric-security universe
deb http://security.ubuntu.com/ubuntu oneiric-security multiverse
deb-src http://security.ubuntu.com/ubuntu oneiric-security multiverse
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;</property>
    

<property name="body">First off, do not use Tomcat from the Ubuntu repository - download it yourself, and extract it in the home directory of the user it will run as.  The example given here is from our xmlbill server.

h5. Step 1: To make Tomcat start automatically, you must create a file in /etc/init.d called tomcat.  Populate the file with the following:
{code}
#!/bin/bash
#
# Startup script for Tomcat server
#
# chkconfig: - 83 53
# description: Starts and stops the Tomcat daemon.
# processname: tomcat
# pidfile: /var/run/tomcat.pid
export JAVA_HOME=/usr/lib/jvm/java-6-sun
export TOMCAT_HOME=/home/billservice/apps/apache-tomcat-6.0.18
export TOMCAT_USER=billservice

# See how we were called.
case $1 in
        start)

su - $TOMCAT_USER -c "sh $TOMCAT_HOME/bin/startup.sh"
        ;;
        stop)
su - $TOMCAT_USER -c "sh $TOMCAT_HOME/bin/shutdown.sh"
        ;;
        restart)
su - $TOMCAT_USER -c "sh $TOMCAT_HOME/bin/shutdown.sh"
su - $TOMCAT_USER -c "sh $TOMCAT_HOME/bin/startup.sh"
        ;;
        *)
                echo "Usage: /etc/init.d/tomcat start|stop|restart"
        ;;
esac

exit 0
{code}

A couple of things to note here; we 'su' to the user we want the process to run as.  This is important because we do NOT want processes running as root.  Additionally, we are explicitly setting the JAVA_HOME environment variable here, but you may wish to set it in /etc/profile (system-wide) or ~.bashrc (user-specific).

h5. Set to start automatically
Run the following commands as root:
{code}
#chmod 755 /etc/init.d/tomcat
#update-rc.d tomcat defaults
{code}
That's it; reboot to verify that everything starts the way you expect.</property>
    

<property name="body">h1. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
FOR UBUNTU SERVER:

chmod 755 suu_tivoli
update-rc.d suu_tivoli defaults

FOR RED HAT:
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc
It will prompt you for your nodename and password.  Once you have entered them, it will drop you at a tsm&gt; prompt.
You can then type 'backup', no quotes, and it will start an incremental backup.  If you don't want to start one right away,
just type 'quit', no quotes, and it will drop you back at the linux prompt.
To start the daemon, run the following command:

#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Server Notes

{code}
Installing TSM Client V5.5.2 on Ubuntu 9.04 Server 64-bit

Note: These instructions are based on the report "TSM-Client unter Debian/etch einrichten" at "https://wiki.gw.dg.de/index.php/TSM:debian"



1) get the latest client - modify version numbers as needed
wget "ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v5r5/Linux/LinuxX86/v552/5.5.2.0-TIV-TSMBAC-LinuxX86.tar"

** NOTE - execute "sudo su -" prior to running the following build and install.  Otherwise, permissions get jacked

2) apt-get install alien ksh ia32-libs

3) unpack the archive
tar xvf 5.5.2.0-TIV-TSMBAC-LinuxX86.tar

4) unpack the RPM archives (ignore warnings re scripts)
alien -g TIVsm-API.i386.rpm
alien -g TIVsm-BA.i386.rpm

5) change directory names
mv TIVsm-API-5.5.1/debian TIVsm-API-5.5.2/DEBIAN
mv TIVsm-BA-5.5.1/debian TIVsm-BA-5.5.2/DEBIAN

6) edit the control files

vi TIVsm-API-5.5.2/DEBIAN/control
Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-api
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-api
Architecture: amd64
Depends:
Description: the API IBM Tivoli Storage Manager API
Version: 5.5.2
&lt;blank line&gt;

Save and exit the file.

vi TIVsm-BA-5.5.2/DEBIAN/control

Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-ba
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-ba
Architecture: amd64
Depends:
Description: the Backup Archive Client IBM Tivoli Storage Manager Client
Version: 5.5.2
&lt;blank line&gt;

Save and exit the file

7) create *.deb packages
dpkg -b TIVsm-API-5.5.2
dpkg -b TIVsm-BA-5.5.2

8) install *.deb packages
dpkg -i TIVsm-API-5.5.2.deb
dpkg -i TIVsm-BA-5.5.2.deb

9)
cd /tmp
wget [http://security.ubuntu.com/ubuntu/pool/universe/i/ia32-libs/ia32-libs_2.7ubuntu6.1_amd64.deb]
dpkg-deb \-x ia32-libs_2.7ubuntu6.1_amd64.deb ia32-libs
sudo cp ia32-libs/usr/lib32/libstdc++.so.5.0.7 /usr/lib32/
cd /usr/lib32
sudo ln \-s libstdc\++.so.5.0.7 libstdc+\+.so.5
10) create/modify TSM configuration files
 (use examples listed above)
vi /opt/tivoli/tsm/client/ba/bin/dsm.opt
vi /opt/tivoli/tsm/client/ba/bin/dsm.sys

11) Run the "Error loading shared libraries" fix located above; run the "English message repository not found" fix as well

12) Link the necessary shared libraries:
add the dsm binary path on a line in the file /etc/ld.so.conf
/opt/tivoli/tsm/client/api/bin
import the shared objects using the command
ldconfig
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/

13) run an incremental backup
dsmc incremental

14) start the TSM scheduler
#/etc/init.d/suu_tivoli start
{code}</property>
    

<property name="body">h1. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
FOR UBUNTU SERVER:

chmod 755 suu_tivoli
update-rc.d suu_tivoli defaults

FOR RED HAT:
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc
It will prompt you for your nodename and password.  Once you have entered them, it will drop you at a tsm&gt; prompt.
You can then type 'backup', no quotes, and it will start an incremental backup.  If you don't want to start one right away,
just type 'quit', no quotes, and it will drop you back at the linux prompt.
To start the daemon, run the following command:

#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Server Notes

{code}
Installing TSM Client V5.5.2 on Ubuntu 9.04 Server 64-bit

Note: These instructions are based on the report "TSM-Client unter Debian/etch einrichten" at "https://wiki.gw.dg.de/index.php/TSM:debian"



1) get the latest client - modify version numbers as needed
wget "ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v5r5/Linux/LinuxX86/v553/5.5.3.0-TIV-TSMBAC-LinuxX86.tar"

** NOTE - execute "sudo su -" prior to running the following build and install.  Otherwise, permissions get jacked

2) apt-get install alien ksh ia32-libs

3) unpack the archive
tar xvf 5.5.2.0-TIV-TSMBAC-LinuxX86.tar

4) unpack the RPM archives (ignore warnings re scripts)
alien -g TIVsm-API.i386.rpm
alien -g TIVsm-BA.i386.rpm

5) change directory names
mv TIVsm-API-5.5.1/debian TIVsm-API-5.5.2/DEBIAN
mv TIVsm-BA-5.5.1/debian TIVsm-BA-5.5.2/DEBIAN

6) edit the control files

vi TIVsm-API-5.5.2/DEBIAN/control
Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-api
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-api
Architecture: amd64
Depends:
Description: the API IBM Tivoli Storage Manager API
Version: 5.5.2
&lt;blank line&gt;

Save and exit the file.

vi TIVsm-BA-5.5.2/DEBIAN/control

Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-ba
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-ba
Architecture: amd64
Depends:
Description: the Backup Archive Client IBM Tivoli Storage Manager Client
Version: 5.5.2
&lt;blank line&gt;

Save and exit the file

7) create *.deb packages
dpkg -b TIVsm-API-5.5.2
dpkg -b TIVsm-BA-5.5.2

8) install *.deb packages
dpkg -i TIVsm-API-5.5.2.deb
dpkg -i TIVsm-BA-5.5.2.deb

9)
cd /tmp
wget [http://security.ubuntu.com/ubuntu/pool/universe/i/ia32-libs/ia32-libs_2.7ubuntu6.1_amd64.deb]
dpkg-deb \-x ia32-libs_2.7ubuntu6.1_amd64.deb ia32-libs
sudo cp ia32-libs/usr/lib32/libstdc++.so.5.0.7 /usr/lib32/
cd /usr/lib32
sudo ln \-s libstdc\++.so.5.0.7 libstdc+\+.so.5
10) create/modify TSM configuration files
 (use examples listed above)
vi /opt/tivoli/tsm/client/ba/bin/dsm.opt
vi /opt/tivoli/tsm/client/ba/bin/dsm.sys

11) Run the "Error loading shared libraries" fix located above; run the "English message repository not found" fix as well

12) Link the necessary shared libraries:
add the dsm binary path on a line in the file /etc/ld.so.conf
/opt/tivoli/tsm/client/api/bin
import the shared objects using the command
ldconfig
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/

13) run an incremental backup
dsmc incremental

14) start the TSM scheduler
#/etc/init.d/suu_tivoli start
{code}</property>
    

<property name="body">h1. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
FOR UBUNTU SERVER:

chmod 755 suu_tivoli
update-rc.d suu_tivoli defaults

FOR RED HAT:
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc
It will prompt you for your nodename and password.  Once you have entered them, it will drop you at a tsm&gt; prompt.
You can then type 'backup', no quotes, and it will start an incremental backup.  If you don't want to start one right away,
just type 'quit', no quotes, and it will drop you back at the linux prompt.
To start the daemon, run the following command:

#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Server Notes

{code}
Installing TSM Client V5.5.2 on Ubuntu 9.04 Server 64-bit

Note: These instructions are based on the report "TSM-Client unter Debian/etch einrichten" at "https://wiki.gw.dg.de/index.php/TSM:debian"



1) get the latest client - modify version numbers as needed
wget "ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v5r5/Linux/LinuxX86/v553/5.5.3.0-TIV-TSMBAC-LinuxX86.tar"

** NOTE - execute "sudo su -" prior to running the following build and install.  Otherwise, permissions get jacked

2) apt-get install alien ksh ia32-libs

3) unpack the archive
tar xvf 5.5.3.0-TIV-TSMBAC-LinuxX86.tar

4) unpack the RPM archives (ignore warnings re scripts)
alien -g TIVsm-API.i386.rpm
alien -g TIVsm-BA.i386.rpm

5) change directory names
mv TIVsm-API-5.5.3/debian TIVsm-API-5.5.3/DEBIAN
mv TIVsm-BA-5.5.3/debian TIVsm-BA-5.5.3/DEBIAN

6) edit the control files

vi TIVsm-API-5.5.3/DEBIAN/control
Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-api
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-api
Architecture: amd64
Depends:
Description: the API IBM Tivoli Storage Manager API
Version: 5.5.3
&lt;blank line&gt;

Save and exit the file.

vi TIVsm-BA-5.5.3/DEBIAN/control

Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-ba
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-ba
Architecture: amd64
Depends:
Description: the Backup Archive Client IBM Tivoli Storage Manager Client
Version: 5.5.3
&lt;blank line&gt;

Save and exit the file

7) create *.deb packages
dpkg -b TIVsm-API-5.5.3
dpkg -b TIVsm-BA-5.5.3

8) install *.deb packages
dpkg -i TIVsm-API-5.5.3.deb
dpkg -i TIVsm-BA-5.5.3.deb

9)
cd /tmp
wget [http://security.ubuntu.com/ubuntu/pool/universe/i/ia32-libs/ia32-libs_2.7ubuntu6.1_amd64.deb]
dpkg-deb \-x ia32-libs_2.7ubuntu6.1_amd64.deb ia32-libs
sudo cp ia32-libs/usr/lib32/libstdc++.so.5.0.7 /usr/lib32/
cd /usr/lib32
sudo ln \-s libstdc\++.so.5.0.7 libstdc+\+.so.5
10) create/modify TSM configuration files
 (use examples listed above)
vi /opt/tivoli/tsm/client/ba/bin/dsm.opt
vi /opt/tivoli/tsm/client/ba/bin/dsm.sys

11) Run the "Error loading shared libraries" fix located above; run the "English message repository not found" fix as well

12) Link the necessary shared libraries:
add the dsm binary path on a line in the file /etc/ld.so.conf
/opt/tivoli/tsm/client/api/bin
import the shared objects using the command
ldconfig
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/

13) run an incremental backup
dsmc incremental

14) start the TSM scheduler
#/etc/init.d/suu_tivoli start
{code}</property>
    

<property name="body">h1. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
FOR UBUNTU SERVER:

chmod 755 suu_tivoli
update-rc.d suu_tivoli defaults

FOR RED HAT:
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc
It will prompt you for your nodename and password.  Once you have entered them, it will drop you at a tsm&gt; prompt.
You can then type 'backup', no quotes, and it will start an incremental backup.  If you don't want to start one right away,
just type 'quit', no quotes, and it will drop you back at the linux prompt.
To start the daemon, run the following command:

#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Server Notes

{code}
Installing TSM Client V5.5.2 on Ubuntu 9.04 Server 64-bit

Note: These instructions are based on the report "TSM-Client unter Debian/etch einrichten" at "https://wiki.gw.dg.de/index.php/TSM:debian"



1) get the latest client - modify version numbers as needed
wget "ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v5r5/Linux/LinuxX86/v553/5.5.3.0-TIV-TSMBAC-LinuxX86.tar"

** NOTE - execute "sudo su -" prior to running the following build and install.  Otherwise, permissions get jacked

2) apt-get install alien ksh ia32-libs gawk

3) unpack the archive
tar xvf 5.5.3.0-TIV-TSMBAC-LinuxX86.tar

4) unpack the RPM archives (ignore warnings re scripts)
alien -g TIVsm-API.i386.rpm
alien -g TIVsm-BA.i386.rpm

5) change directory names
mv TIVsm-API-5.5.3/debian TIVsm-API-5.5.3/DEBIAN
mv TIVsm-BA-5.5.3/debian TIVsm-BA-5.5.3/DEBIAN

6) edit the control files

vi TIVsm-API-5.5.3/DEBIAN/control
Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-api
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-api
Architecture: amd64
Depends:
Description: the API IBM Tivoli Storage Manager API
Version: 5.5.3
&lt;blank line&gt;

Save and exit the file.

vi TIVsm-BA-5.5.3/DEBIAN/control

Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-ba
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-ba
Architecture: amd64
Depends:
Description: the Backup Archive Client IBM Tivoli Storage Manager Client
Version: 5.5.3
&lt;blank line&gt;

Save and exit the file

7) create *.deb packages
dpkg -b TIVsm-API-5.5.3
dpkg -b TIVsm-BA-5.5.3

8) install *.deb packages
dpkg -i TIVsm-API-5.5.3.deb
dpkg -i TIVsm-BA-5.5.3.deb

9)
cd /tmp
wget [http://security.ubuntu.com/ubuntu/pool/universe/i/ia32-libs/ia32-libs_2.7ubuntu6.1_amd64.deb]
dpkg-deb \-x ia32-libs_2.7ubuntu6.1_amd64.deb ia32-libs
sudo cp ia32-libs/usr/lib32/libstdc++.so.5.0.7 /usr/lib32/
cd /usr/lib32
sudo ln \-s libstdc\++.so.5.0.7 libstdc+\+.so.5
10) create/modify TSM configuration files
 (use examples listed above)
vi /opt/tivoli/tsm/client/ba/bin/dsm.opt
vi /opt/tivoli/tsm/client/ba/bin/dsm.sys

11) Run the "Error loading shared libraries" fix located above; run the "English message repository not found" fix as well

12) Link the necessary shared libraries:
add the dsm binary path on a line in the file /etc/ld.so.conf
/opt/tivoli/tsm/client/api/bin
import the shared objects using the command
ldconfig
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/

13) run an incremental backup
dsmc incremental

14) start the TSM scheduler
#/etc/init.d/suu_tivoli start
{code}</property>
    

<property name="body">h1. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
FOR UBUNTU SERVER:

chmod 755 suu_tivoli
update-rc.d suu_tivoli defaults

FOR RED HAT:
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc
It will prompt you for your nodename and password.  Once you have entered them, it will drop you at a tsm&gt; prompt.
You can then type 'backup', no quotes, and it will start an incremental backup.  If you don't want to start one right away,
just type 'quit', no quotes, and it will drop you back at the linux prompt.
To start the daemon, run the following command:

#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Server Notes

{code}
Installing TSM Client V5.5.2 on Ubuntu 9.04 Server 64-bit

Note: These instructions are based on the report "TSM-Client unter Debian/etch einrichten" at "https://wiki.gw.dg.de/index.php/TSM:debian"



1) get the latest client - modify version numbers as needed
wget "ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v5r5/Linux/LinuxX86/v553/5.5.3.0-TIV-TSMBAC-LinuxX86.tar"

** NOTE - execute "sudo su -" prior to running the following build and install.  Otherwise, permissions get jacked

2) apt-get install alien ksh ia32-libs gawk

3) unpack the archive
tar xvf 5.5.3.0-TIV-TSMBAC-LinuxX86.tar

4) unpack the RPM archives (ignore warnings re scripts)
alien -g TIVsm-API.i386.rpm
alien -g TIVsm-BA.i386.rpm

5) change directory names
mv TIVsm-API-5.5.3/debian TIVsm-API-5.5.3/DEBIAN
mv TIVsm-BA-5.5.3/debian TIVsm-BA-5.5.3/DEBIAN

6) edit the control files

vi TIVsm-API-5.5.3/DEBIAN/control
Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-api
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-api
Architecture: amd64
Depends:
Description: the API IBM Tivoli Storage Manager API
Version: 5.5.3
&lt;blank line&gt;

Save and exit the file.

vi TIVsm-BA-5.5.3/DEBIAN/control

Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-ba
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-ba
Architecture: amd64
Depends:
Description: the Backup Archive Client IBM Tivoli Storage Manager Client
Version: 5.5.3
&lt;blank line&gt;

Save and exit the file

7) create *.deb packages
dpkg -b TIVsm-API-5.5.3
dpkg -b TIVsm-BA-5.5.3

8) install *.deb packages
dpkg -i TIVsm-API-5.5.3.deb
dpkg -i TIVsm-BA-5.5.3.deb

9)
cd /tmp
wget [http://security.ubuntu.com/ubuntu/pool/universe/i/ia32-libs/ia32-libs_20090808ubuntu9_amd64.deb]
dpkg-deb \-x ia32-libs_20090808ubuntu9_amd64.deb ia32-libs
sudo cp ia32-libs/usr/lib32/libstdc++.so.5.0.7 /usr/lib32/
cd /usr/lib32
sudo ln \-s libstdc\++.so.5.0.7 libstdc+\+.so.5
10) create/modify TSM configuration files
 (use examples listed above)
vi /opt/tivoli/tsm/client/ba/bin/dsm.opt
vi /opt/tivoli/tsm/client/ba/bin/dsm.sys

11) Run the "Error loading shared libraries" fix located above; run the "English message repository not found" fix as well

12) Link the necessary shared libraries:
add the dsm binary path on a line in the file /etc/ld.so.conf
/opt/tivoli/tsm/client/api/bin
import the shared objects using the command
ldconfig
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/

13) run an incremental backup
dsmc incremental

14) start the TSM scheduler
#/etc/init.d/suu_tivoli start
{code}</property>
    

<property name="body">h1. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Example dsm.sys file - Ubuntu Server 64-bit
{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMMethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu
nodename WIKI
passwordaccess generate
MANAGEDSERVICES schedule webclient
virtualmount /
virtualmount /home
virtualmount /etc
include /home/.../*
include /etc/.../*
exclude.dir /bin
exclude.dir /boot
exclude.dir /dev
exclude.dir /initrd
exclude.dir /lib
exclude.dir /lost*
exclude.dir /media
exclude.dir /mnt
exclude.dir /opt
exclude.dir /proc
exclude.dir /root
exclude.dir /sbin
exclude.dir /srv
exclude.dir /tmp
exclude.dir /var
exclude.dir /usr/bin
exclude.dir /usr/games
exclude.dir /usr/include
exclude.dir /usr/lib
exclude.dir /usr/sbin
exclude.dir /usr/share
exclude.dir /usr/src
exclude.dir /usr/X11R6
exclude.dir /usr/local/bin
exclude.dir /usr/local/etc
exclude.dir /usr/local/games
exclude.dir /usr/local/include
exclude.dir /usr/local/lib
exclude.dir /usr/local/sbin
exclude.dir /usr/local/share
exclude.dir /usr/local/src
{code}

h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
FOR UBUNTU SERVER:

chmod 755 suu_tivoli
update-rc.d suu_tivoli defaults

FOR RED HAT:
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc
It will prompt you for your nodename and password.  Once you have entered them, it will drop you at a tsm&gt; prompt.
You can then type 'backup', no quotes, and it will start an incremental backup.  If you don't want to start one right away,
just type 'quit', no quotes, and it will drop you back at the linux prompt.
To start the daemon, run the following command:

#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Server Notes

{code}
Installing TSM Client V5.5.2 on Ubuntu 9.04 Server 64-bit

Note: These instructions are based on the report "TSM-Client unter Debian/etch einrichten" at "https://wiki.gw.dg.de/index.php/TSM:debian"



1) get the latest client - modify version numbers as needed
wget "ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v5r5/Linux/LinuxX86/v553/5.5.3.0-TIV-TSMBAC-LinuxX86.tar"

** NOTE - execute "sudo su -" prior to running the following build and install.  Otherwise, permissions get jacked

2) apt-get install alien ksh ia32-libs gawk

3) unpack the archive
tar xvf 5.5.3.0-TIV-TSMBAC-LinuxX86.tar

4) unpack the RPM archives (ignore warnings re scripts)
alien -g TIVsm-API.i386.rpm
alien -g TIVsm-BA.i386.rpm

5) change directory names
mv TIVsm-API-5.5.3/debian TIVsm-API-5.5.3/DEBIAN
mv TIVsm-BA-5.5.3/debian TIVsm-BA-5.5.3/DEBIAN

6) edit the control files

vi TIVsm-API-5.5.3/DEBIAN/control
Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-api
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-api
Architecture: amd64
Depends:
Description: the API IBM Tivoli Storage Manager API
Version: 5.5.3
&lt;blank line&gt;

Save and exit the file.

vi TIVsm-BA-5.5.3/DEBIAN/control

Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-ba
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-ba
Architecture: amd64
Depends:
Description: the Backup Archive Client IBM Tivoli Storage Manager Client
Version: 5.5.3
&lt;blank line&gt;

Save and exit the file

7) create *.deb packages
dpkg -b TIVsm-API-5.5.3
dpkg -b TIVsm-BA-5.5.3

8) install *.deb packages
dpkg -i TIVsm-API-5.5.3.deb
dpkg -i TIVsm-BA-5.5.3.deb

9)
cd /tmp
wget [http://security.ubuntu.com/ubuntu/pool/universe/i/ia32-libs/ia32-libs_20090808ubuntu9_amd64.deb]
dpkg-deb \-x ia32-libs_20090808ubuntu9_amd64.deb ia32-libs
sudo cp ia32-libs/usr/lib32/libstdc++.so.5.0.7 /usr/lib32/
cd /usr/lib32
sudo ln \-s libstdc\++.so.5.0.7 libstdc+\+.so.5
10) create/modify TSM configuration files
 (use examples listed above)
vi /opt/tivoli/tsm/client/ba/bin/dsm.opt
vi /opt/tivoli/tsm/client/ba/bin/dsm.sys

11) Run the "Error loading shared libraries" fix located above; run the "English message repository not found" fix as well

12) Link the necessary shared libraries:
add the dsm binary path on a line in the file /etc/ld.so.conf
/opt/tivoli/tsm/client/api/bin
import the shared objects using the command
ldconfig
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/

13) run an incremental backup
dsmc incremental

14) start the TSM scheduler
#/etc/init.d/suu_tivoli start
{code}</property>
    

<property name="body">h1. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Example dsm.sys file - Ubuntu Server 64-bit
{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMMethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu
nodename WIKI
passwordaccess generate
MANAGEDSERVICES schedule webclient
virtualmountpoint /
virtualmountpoint /home
virtualmountpoint /etc
include /home/.../*
include /etc/.../*
exclude.dir /bin
exclude.dir /boot
exclude.dir /dev
exclude.dir /initrd
exclude.dir /lib
exclude.dir /lost*
exclude.dir /media
exclude.dir /mnt
exclude.dir /opt
exclude.dir /proc
exclude.dir /root
exclude.dir /sbin
exclude.dir /srv
exclude.dir /tmp
exclude.dir /var
exclude.dir /usr/bin
exclude.dir /usr/games
exclude.dir /usr/include
exclude.dir /usr/lib
exclude.dir /usr/sbin
exclude.dir /usr/share
exclude.dir /usr/src
exclude.dir /usr/X11R6
exclude.dir /usr/local/bin
exclude.dir /usr/local/etc
exclude.dir /usr/local/games
exclude.dir /usr/local/include
exclude.dir /usr/local/lib
exclude.dir /usr/local/sbin
exclude.dir /usr/local/share
exclude.dir /usr/local/src
{code}

h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
FOR UBUNTU SERVER:

chmod 755 suu_tivoli
update-rc.d suu_tivoli defaults

FOR RED HAT:
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc
It will prompt you for your nodename and password.  Once you have entered them, it will drop you at a tsm&gt; prompt.
You can then type 'backup', no quotes, and it will start an incremental backup.  If you don't want to start one right away,
just type 'quit', no quotes, and it will drop you back at the linux prompt.
To start the daemon, run the following command:

#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Server Notes

{code}
Installing TSM Client V5.5.2 on Ubuntu 9.04 Server 64-bit

Note: These instructions are based on the report "TSM-Client unter Debian/etch einrichten" at "https://wiki.gw.dg.de/index.php/TSM:debian"



1) get the latest client - modify version numbers as needed
wget "ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v5r5/Linux/LinuxX86/v553/5.5.3.0-TIV-TSMBAC-LinuxX86.tar"

** NOTE - execute "sudo su -" prior to running the following build and install.  Otherwise, permissions get jacked

2) apt-get install alien ksh ia32-libs gawk

3) unpack the archive
tar xvf 5.5.3.0-TIV-TSMBAC-LinuxX86.tar

4) unpack the RPM archives (ignore warnings re scripts)
alien -g TIVsm-API.i386.rpm
alien -g TIVsm-BA.i386.rpm

5) change directory names
mv TIVsm-API-5.5.3/debian TIVsm-API-5.5.3/DEBIAN
mv TIVsm-BA-5.5.3/debian TIVsm-BA-5.5.3/DEBIAN

6) edit the control files

vi TIVsm-API-5.5.3/DEBIAN/control
Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-api
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-api
Architecture: amd64
Depends:
Description: the API IBM Tivoli Storage Manager API
Version: 5.5.3
&lt;blank line&gt;

Save and exit the file.

vi TIVsm-BA-5.5.3/DEBIAN/control

Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-ba
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-ba
Architecture: amd64
Depends:
Description: the Backup Archive Client IBM Tivoli Storage Manager Client
Version: 5.5.3
&lt;blank line&gt;

Save and exit the file

7) create *.deb packages
dpkg -b TIVsm-API-5.5.3
dpkg -b TIVsm-BA-5.5.3

8) install *.deb packages
dpkg -i TIVsm-API-5.5.3.deb
dpkg -i TIVsm-BA-5.5.3.deb

9)
cd /tmp
wget [http://security.ubuntu.com/ubuntu/pool/universe/i/ia32-libs/ia32-libs_20090808ubuntu9_amd64.deb]
dpkg-deb \-x ia32-libs_20090808ubuntu9_amd64.deb ia32-libs
sudo cp ia32-libs/usr/lib32/libstdc++.so.5.0.7 /usr/lib32/
cd /usr/lib32
sudo ln \-s libstdc\++.so.5.0.7 libstdc+\+.so.5
10) create/modify TSM configuration files
 (use examples listed above)
vi /opt/tivoli/tsm/client/ba/bin/dsm.opt
vi /opt/tivoli/tsm/client/ba/bin/dsm.sys

11) Run the "Error loading shared libraries" fix located above; run the "English message repository not found" fix as well

12) Link the necessary shared libraries:
add the dsm binary path on a line in the file /etc/ld.so.conf
/opt/tivoli/tsm/client/api/bin
import the shared objects using the command
ldconfig
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/

13) run an incremental backup
dsmc incremental

14) start the TSM scheduler
#/etc/init.d/suu_tivoli start
{code}</property>
    

<property name="body">h4. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Example dsm.sys file - Ubuntu Server 64-bit
{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMMethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu
nodename WIKI
passwordaccess generate
MANAGEDSERVICES schedule webclient
virtualmountpoint /
virtualmountpoint /home
virtualmountpoint /etc
include /home/.../*
include /etc/.../*
exclude.dir /bin
exclude.dir /boot
exclude.dir /dev
exclude.dir /initrd
exclude.dir /lib
exclude.dir /lost*
exclude.dir /media
exclude.dir /mnt
exclude.dir /opt
exclude.dir /proc
exclude.dir /root
exclude.dir /sbin
exclude.dir /srv
exclude.dir /tmp
exclude.dir /var
exclude.dir /usr/bin
exclude.dir /usr/games
exclude.dir /usr/include
exclude.dir /usr/lib
exclude.dir /usr/sbin
exclude.dir /usr/share
exclude.dir /usr/src
exclude.dir /usr/X11R6
exclude.dir /usr/local/bin
exclude.dir /usr/local/etc
exclude.dir /usr/local/games
exclude.dir /usr/local/include
exclude.dir /usr/local/lib
exclude.dir /usr/local/sbin
exclude.dir /usr/local/share
exclude.dir /usr/local/src
{code}

h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
export LANG=en_US;
export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
FOR UBUNTU SERVER:

chmod 755 suu_tivoli
update-rc.d suu_tivoli defaults

FOR RED HAT:
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc
It will prompt you for your nodename and password.  Once you have entered them, it will drop you at a tsm&gt; prompt.
You can then type 'backup', no quotes, and it will start an incremental backup.  If you don't want to start one right away,
just type 'quit', no quotes, and it will drop you back at the linux prompt.
To start the daemon, run the following command:

#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Server Notes

{code}
Installing TSM Client V5.5.2 on Ubuntu 9.04 Server 64-bit

Note: These instructions are based on the report "TSM-Client unter Debian/etch einrichten" at "https://wiki.gw.dg.de/index.php/TSM:debian"



1) get the latest client - modify version numbers as needed
wget "ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v5r5/Linux/LinuxX86/v553/5.5.3.0-TIV-TSMBAC-LinuxX86.tar"

** NOTE - execute "sudo su -" prior to running the following build and install.  Otherwise, permissions get jacked

2) apt-get install alien ksh ia32-libs gawk

3) unpack the archive
tar xvf 5.5.3.0-TIV-TSMBAC-LinuxX86.tar

4) unpack the RPM archives (ignore warnings re scripts)
alien -g TIVsm-API.i386.rpm
alien -g TIVsm-BA.i386.rpm

5) change directory names
mv TIVsm-API-5.5.3/debian TIVsm-API-5.5.3/DEBIAN
mv TIVsm-BA-5.5.3/debian TIVsm-BA-5.5.3/DEBIAN

6) edit the control files

vi TIVsm-API-5.5.3/DEBIAN/control
Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-api
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-api
Architecture: amd64
Depends:
Description: the API IBM Tivoli Storage Manager API
Version: 5.5.3
&lt;blank line&gt;

Save and exit the file.

vi TIVsm-BA-5.5.3/DEBIAN/control

Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-ba
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-ba
Architecture: amd64
Depends:
Description: the Backup Archive Client IBM Tivoli Storage Manager Client
Version: 5.5.3
&lt;blank line&gt;

Save and exit the file

7) create *.deb packages
dpkg -b TIVsm-API-5.5.3
dpkg -b TIVsm-BA-5.5.3

8) install *.deb packages
dpkg -i TIVsm-API-5.5.3.deb
dpkg -i TIVsm-BA-5.5.3.deb

9)
cd /tmp
wget [http://security.ubuntu.com/ubuntu/pool/universe/i/ia32-libs/ia32-libs_20090808ubuntu9_amd64.deb]
dpkg-deb \-x ia32-libs_20090808ubuntu9_amd64.deb ia32-libs
sudo cp ia32-libs/usr/lib32/libstdc++.so.5.0.7 /usr/lib32/
cd /usr/lib32
sudo ln \-s libstdc\++.so.5.0.7 libstdc+\+.so.5
10) create/modify TSM configuration files
 (use examples listed above)
vi /opt/tivoli/tsm/client/ba/bin/dsm.opt
vi /opt/tivoli/tsm/client/ba/bin/dsm.sys

11) Run the "Error loading shared libraries" fix located above; run the "English message repository not found" fix as well

12) Link the necessary shared libraries:
add the dsm binary path on a line in the file /etc/ld.so.conf
/opt/tivoli/tsm/client/api/bin
import the shared objects using the command
ldconfig
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/

13) run an incremental backup
dsmc incremental

14) start the TSM scheduler
#/etc/init.d/suu_tivoli start
{code}</property>
    

<property name="body">h4. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Example dsm.sys file - Ubuntu Server 64-bit
{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMMethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu
nodename WIKI
passwordaccess generate
MANAGEDSERVICES schedule webclient
virtualmountpoint /
virtualmountpoint /home
virtualmountpoint /etc
include /home/.../*
include /etc/.../*
exclude.dir /bin
exclude.dir /boot
exclude.dir /dev
exclude.dir /initrd
exclude.dir /lib
exclude.dir /lost*
exclude.dir /media
exclude.dir /mnt
exclude.dir /opt
exclude.dir /proc
exclude.dir /root
exclude.dir /sbin
exclude.dir /srv
exclude.dir /tmp
exclude.dir /var
exclude.dir /usr/bin
exclude.dir /usr/games
exclude.dir /usr/include
exclude.dir /usr/lib
exclude.dir /usr/sbin
exclude.dir /usr/share
exclude.dir /usr/src
exclude.dir /usr/X11R6
exclude.dir /usr/local/bin
exclude.dir /usr/local/etc
exclude.dir /usr/local/games
exclude.dir /usr/local/include
exclude.dir /usr/local/lib
exclude.dir /usr/local/sbin
exclude.dir /usr/local/share
exclude.dir /usr/local/src
{code}

h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
#export LANG=en_US;
#export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
FOR UBUNTU SERVER:

chmod 755 suu_tivoli
update-rc.d suu_tivoli defaults

FOR RED HAT:
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc
It will prompt you for your nodename and password.  Once you have entered them, it will drop you at a tsm&gt; prompt.
You can then type 'backup', no quotes, and it will start an incremental backup.  If you don't want to start one right away,
just type 'quit', no quotes, and it will drop you back at the linux prompt.
To start the daemon, run the following command:

#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Server Notes

{code}
Installing TSM Client V5.5.2 on Ubuntu 9.04 Server 64-bit

Note: These instructions are based on the report "TSM-Client unter Debian/etch einrichten" at "https://wiki.gw.dg.de/index.php/TSM:debian"



1) get the latest client - modify version numbers as needed
wget "ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v5r5/Linux/LinuxX86/v553/5.5.3.0-TIV-TSMBAC-LinuxX86.tar"

** NOTE - execute "sudo su -" prior to running the following build and install.  Otherwise, permissions get jacked

2) apt-get install alien ksh ia32-libs gawk

3) unpack the archive
tar xvf 5.5.3.0-TIV-TSMBAC-LinuxX86.tar

4) unpack the RPM archives (ignore warnings re scripts)
alien -g TIVsm-API.i386.rpm
alien -g TIVsm-BA.i386.rpm

5) change directory names
mv TIVsm-API-5.5.3/debian TIVsm-API-5.5.3/DEBIAN
mv TIVsm-BA-5.5.3/debian TIVsm-BA-5.5.3/DEBIAN

6) edit the control files

vi TIVsm-API-5.5.3/DEBIAN/control
Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-api
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-api
Architecture: amd64
Depends:
Description: the API IBM Tivoli Storage Manager API
Version: 5.5.3
&lt;blank line&gt;

Save and exit the file.

vi TIVsm-BA-5.5.3/DEBIAN/control

Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-ba
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-ba
Architecture: amd64
Depends:
Description: the Backup Archive Client IBM Tivoli Storage Manager Client
Version: 5.5.3
&lt;blank line&gt;

Save and exit the file

7) create *.deb packages
dpkg -b TIVsm-API-5.5.3
dpkg -b TIVsm-BA-5.5.3

8) install *.deb packages
dpkg -i TIVsm-API-5.5.3.deb
dpkg -i TIVsm-BA-5.5.3.deb

9)
cd /tmp
wget [http://security.ubuntu.com/ubuntu/pool/universe/i/ia32-libs/ia32-libs_20090808ubuntu9_amd64.deb]
dpkg-deb \-x ia32-libs_20090808ubuntu9_amd64.deb ia32-libs
sudo cp ia32-libs/usr/lib32/libstdc++.so.5.0.7 /usr/lib32/
cd /usr/lib32
sudo ln \-s libstdc\++.so.5.0.7 libstdc+\+.so.5
10) create/modify TSM configuration files
 (use examples listed above)
vi /opt/tivoli/tsm/client/ba/bin/dsm.opt
vi /opt/tivoli/tsm/client/ba/bin/dsm.sys

11) Run the "Error loading shared libraries" fix located above; run the "English message repository not found" fix as well

12) Link the necessary shared libraries:
add the dsm binary path on a line in the file /etc/ld.so.conf
/opt/tivoli/tsm/client/api/bin
import the shared objects using the command
ldconfig
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/

13) run an incremental backup
dsmc incremental

14) start the TSM scheduler
#/etc/init.d/suu_tivoli start
{code}</property>
    

<property name="body">&lt;h3&gt;Create log4j.properties file&lt;/h3&gt;

&lt;p&gt;Create a log4j.properties file in the $CATALINA_HOME/lib directory with the following contents (modify file size as desired):&lt;/p&gt;
&lt;ac:structured-macro ac:macro-id="494771eb-cd14-4e8b-b984-bcddfd89257f" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
log4j.rootLogger=INFO, CATALINA

# Define all the appenders
log4j.appender.CATALINA=org.apache.log4j.RollingFileAppender
log4j.appender.CATALINA.file=${catalina.base}/logs/catalina.log
log4j.appender.CATALINA.MaxFileSize=50MB
log4j.appender.CATALINA.MaxBackupIndex=200
log4j.appender.CATALINA.layout=org.apache.log4j.PatternLayout
log4j.appender.CATALINA.append=true
log4j.rootCategory=ALL, CATALINA
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;

&lt;h3&gt;Download JAR files&lt;/h3&gt;

&lt;p&gt;Obtain a copy of all JAR files from the sherpa server under Tomcat\log4j folder&lt;/p&gt;

&lt;h3&gt;Stop Tomcat, place JARs in directories&lt;/h3&gt;

&lt;p&gt;Stop Tomcat&lt;/p&gt;

&lt;p&gt;Place the log4j-1.2.x.jar in $CATALINA_HOME/lib.&lt;br /&gt;
Replace $CATALINA_HOME/bin/tomcat-juli.jar with downloaded tomcat-juli.jar&lt;br /&gt;
Place downloaded tomcat-juli-adapters.jar in $CATALINA_HOME/lib&lt;br /&gt;
Delete $CATALINA_BASE/conf/logging.properties to prevent java.util.logging generating zero length log files&lt;/p&gt;

&lt;p&gt;Start Tomcat&lt;/p&gt;</property>
    

<property name="body">h3. Create log4j.properties file
Create a log4j.properties file in the $CATALINA_HOME/lib directory with the following contents (modify file size as desired):
{code}
log4j.rootLogger=INFO, R 
log4j.appender.R=org.apache.log4j.RollingFileAppender 
log4j.appender.R.File=${catalina.base}/logs/tomcat.log 
log4j.appender.R.MaxFileSize=10MB 
log4j.appender.R.MaxBackupIndex=10 
log4j.appender.R.layout=org.apache.log4j.PatternLayout 
log4j.appender.R.layout.ConversionPattern=%p %t %c - %m%n
{code}</property>
    

<property name="body">h4. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Example dsm.sys file - Ubuntu Server 64-bit
{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMMethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu
nodename WIKI
passwordaccess generate
MANAGEDSERVICES schedule webclient
virtualmountpoint /
virtualmountpoint /home
virtualmountpoint /etc
include /home/.../*
include /etc/.../*
exclude.dir /bin
exclude.dir /boot
exclude.dir /dev
exclude.dir /initrd
exclude.dir /lib
exclude.dir /lost*
exclude.dir /media
exclude.dir /mnt
exclude.dir /opt
exclude.dir /proc
exclude.dir /root
exclude.dir /sbin
exclude.dir /srv
exclude.dir /tmp
exclude.dir /var
exclude.dir /usr/bin
exclude.dir /usr/games
exclude.dir /usr/include
exclude.dir /usr/lib
exclude.dir /usr/sbin
exclude.dir /usr/share
exclude.dir /usr/src
exclude.dir /usr/X11R6
exclude.dir /usr/local/bin
exclude.dir /usr/local/etc
exclude.dir /usr/local/games
exclude.dir /usr/local/include
exclude.dir /usr/local/lib
exclude.dir /usr/local/sbin
exclude.dir /usr/local/share
exclude.dir /usr/local/src
{code}

h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
#export LANG=en_US;
#export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
FOR UBUNTU SERVER:

chmod 755 suu_tivoli
update-rc.d suu_tivoli defaults

FOR RED HAT:
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc
It will prompt you for your nodename and password.  Once you have entered them, it will drop you at a tsm&gt; prompt.
You can then type 'backup', no quotes, and it will start an incremental backup.  If you don't want to start one right away,
just type 'quit', no quotes, and it will drop you back at the linux prompt.
To start the daemon, run the following command:

#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Server Notes

{code}
Installing TSM Client V5.5.2 on Ubuntu 9.04 Server 64-bit

Note: These instructions are based on the report "TSM-Client unter Debian/etch einrichten" at "https://wiki.gw.dg.de/index.php/TSM:debian"



1) get the latest client - modify version numbers as needed
wget "ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v5r5/Linux/LinuxX86/v553/5.5.3.0-TIV-TSMBAC-LinuxX86.tar"

** NOTE - execute "sudo su -" prior to running the following build and install.  Otherwise, permissions get jacked

2) apt-get install alien ksh ia32-libs gawk

3) unpack the archive
tar xvf 5.5.3.0-TIV-TSMBAC-LinuxX86.tar

4) unpack the RPM archives (ignore warnings re scripts)
alien -g TIVsm-API.i386.rpm
alien -g TIVsm-BA.i386.rpm

5) change directory names
mv TIVsm-API-5.5.3/debian TIVsm-API-5.5.3/DEBIAN
mv TIVsm-BA-5.5.3/debian TIVsm-BA-5.5.3/DEBIAN

6) edit the control files

vi TIVsm-API-5.5.3/DEBIAN/control
Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-api
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-api
Architecture: amd64
Depends:
Description: the API IBM Tivoli Storage Manager API
Version: 5.5.3
&lt;blank line&gt;

Save and exit the file.

vi TIVsm-BA-5.5.3/DEBIAN/control

Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-ba
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-ba
Architecture: amd64
Depends:
Description: the Backup Archive Client IBM Tivoli Storage Manager Client
Version: 5.5.3
&lt;blank line&gt;

Save and exit the file

7) create *.deb packages
dpkg -b TIVsm-API-5.5.3
dpkg -b TIVsm-BA-5.5.3

8) install *.deb packages
dpkg -i TIVsm-API-5.5.3.deb
dpkg -i TIVsm-BA-5.5.3.deb

9)
cd /tmp
wget [http://security.ubuntu.com/ubuntu/pool/universe/i/ia32-libs/ia32-libs_20090808ubuntu9_amd64.deb]
dpkg-deb \-x ia32-libs_20090808ubuntu9_amd64.deb ia32-libs
sudo cp ia32-libs/usr/lib32/libstdc++.so.5.0.7 /usr/lib32/
cd /usr/lib32
sudo ln \-s libstdc\++.so.5.0.7 libstdc+\+.so.5
10) create/modify TSM configuration files
 (use examples listed above)
vi /opt/tivoli/tsm/client/ba/bin/dsm.opt
vi /opt/tivoli/tsm/client/ba/bin/dsm.sys

11) Run the "Error loading shared libraries" fix located above; run the "English message repository not found" fix as well

12) Link the necessary shared libraries:
add the dsm binary path on a line in the file /etc/ld.so.conf
/opt/tivoli/tsm/client/api/bin
import the shared objects using the command
ldconfig
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/EN_US/

13) run an incremental backup
dsmc incremental

14) start the TSM scheduler
#/etc/init.d/suu_tivoli start
{code}</property>
    

<property name="body">h4. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Example dsm.sys file - Ubuntu Server 64-bit
{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMMethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu
nodename WIKI
passwordaccess generate
MANAGEDSERVICES schedule webclient
virtualmountpoint /
virtualmountpoint /home
virtualmountpoint /etc
include /home/.../*
include /etc/.../*
exclude.dir /bin
exclude.dir /boot
exclude.dir /dev
exclude.dir /initrd
exclude.dir /lib
exclude.dir /lost*
exclude.dir /media
exclude.dir /mnt
exclude.dir /opt
exclude.dir /proc
exclude.dir /root
exclude.dir /sbin
exclude.dir /srv
exclude.dir /tmp
exclude.dir /var
exclude.dir /usr/bin
exclude.dir /usr/games
exclude.dir /usr/include
exclude.dir /usr/lib
exclude.dir /usr/sbin
exclude.dir /usr/share
exclude.dir /usr/src
exclude.dir /usr/X11R6
exclude.dir /usr/local/bin
exclude.dir /usr/local/etc
exclude.dir /usr/local/games
exclude.dir /usr/local/include
exclude.dir /usr/local/lib
exclude.dir /usr/local/sbin
exclude.dir /usr/local/share
exclude.dir /usr/local/src
{code}

h2. Example dsm.sys for Red Hat servers
{code}
SErvername  tivoli
   COMMmethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu

nodename BIRCHINB 
passwordaccess generate
MANAGEDSERVICES	schedule webclient
include /u01/.../*
include /home/.../*
include /etc/.../*
include /root/.../*
exclude.dir /bin
exclude.dir /boot
exclude.dir /boot/grub
exclude.dir /boot/lost+found
exclude.dir /dev
exclude.dir /initrd
exclude.dir /lib
exclude.dir /lib/lsb
exclude.dir /lib/modules
exclude.dir /lib/rtkaio
exclude.dir /lib/security
exclude.dir /lib/udev
exclude.dir /lost+found
exclude.dir /media
exclude.dir /misc
exclude.dir /mnt
exclude.dir /opt
exclude.dir /proc
exclude.dir /root
exclude.dir /sbin
exclude.dir /srv
exclude.dir /selinux
exclude.dir /sys
exclude.dir /tftpboot
exclude.dir /tmp
exclude.dir /var
exclude.dir /usr
{code}
h2. Configuring Automatic Startup


h4. Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
#export LANG=en_US;
#export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
FOR UBUNTU SERVER:

chmod 755 suu_tivoli
update-rc.d suu_tivoli defaults

FOR RED HAT:
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc
It will prompt you for your nodename and password.  Once you have entered them, it will drop you at a tsm&gt; prompt.
You can then type 'backup', no quotes, and it will start an incremental backup.  If you don't want to start one right away,
just type 'quit', no quotes, and it will drop you back at the linux prompt.
To start the daemon, run the following command:

#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Server Notes

{code}
Installing TSM Client V5.5.2 on Ubuntu 9.04 Server 64-bit

Note: These instructions are based on the report "TSM-Client unter Debian/etch einrichten" at "https://wiki.gw.dg.de/index.php/TSM:debian"



1) get the latest client - modify version numbers as needed
wget "ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v5r5/Linux/LinuxX86/v553/5.5.3.0-TIV-TSMBAC-LinuxX86.tar"

** NOTE - execute "sudo su -" prior to running the following build and install.  Otherwise, permissions get jacked

2) apt-get install alien ksh ia32-libs gawk

3) unpack the archive
tar xvf 5.5.3.0-TIV-TSMBAC-LinuxX86.tar

4) unpack the RPM archives (ignore warnings re scripts)
alien -g TIVsm-API.i386.rpm
alien -g TIVsm-BA.i386.rpm

5) change directory names
mv TIVsm-API-5.5.3/debian TIVsm-API-5.5.3/DEBIAN
mv TIVsm-BA-5.5.3/debian TIVsm-BA-5.5.3/DEBIAN

6) edit the control files

vi TIVsm-API-5.5.3/DEBIAN/control
Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-api
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-api
Architecture: amd64
Depends:
Description: the API IBM Tivoli Storage Manager API
Version: 5.5.3
&lt;blank line&gt;

Save and exit the file.

vi TIVsm-BA-5.5.3/DEBIAN/control

Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-ba
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-ba
Architecture: amd64
Depends:
Description: the Backup Archive Client IBM Tivoli Storage Manager Client
Version: 5.5.3
&lt;blank line&gt;

Save and exit the file

7) create *.deb packages
dpkg -b TIVsm-API-5.5.3
dpkg -b TIVsm-BA-5.5.3

8) install *.deb packages
dpkg -i TIVsm-API-5.5.3.deb
dpkg -i TIVsm-BA-5.5.3.deb

9)
cd /tmp
wget [http://security.ubuntu.com/ubuntu/pool/universe/i/ia32-libs/ia32-libs_20090808ubuntu9_amd64.deb]
dpkg-deb \-x ia32-libs_20090808ubuntu9_amd64.deb ia32-libs
sudo cp ia32-libs/usr/lib32/libstdc++.so.5.0.7 /usr/lib32/
cd /usr/lib32
sudo ln \-s libstdc\++.so.5.0.7 libstdc+\+.so.5
10) create/modify TSM configuration files
 (use examples listed above)
vi /opt/tivoli/tsm/client/ba/bin/dsm.opt
vi /opt/tivoli/tsm/client/ba/bin/dsm.sys

11) Run the "Error loading shared libraries" fix located above; run the "English message repository not found" fix as well

12) Link the necessary shared libraries:
add the dsm binary path on a line in the file /etc/ld.so.conf
/opt/tivoli/tsm/client/api/bin
import the shared objects using the command
ldconfig
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/EN_US/

13) run an incremental backup
dsmc incremental

14) start the TSM scheduler
#/etc/init.d/suu_tivoli start
{code}</property>
    

<property name="body">&lt;h3&gt;Server-side config files&lt;/h3&gt;&lt;h5&gt;/etc/services&lt;/h5&gt;&lt;p&gt;Append the following lines to the end of the file:&lt;/p&gt;&lt;ac:structured-macro ac:macro-id="c01c70c1-3dd6-45f9-840e-c0cf66349a18" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[# Local services
rquotad         4003/tcp
rquotad         4003/udp
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;h5&gt;/etc/exports&lt;/h5&gt;&lt;ac:structured-macro ac:macro-id="38d9c3cf-d3f0-41e5-aaf5-1e0c70e7e200" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[/usr/local/jobout 134.250.7.110(rw,sync) 134.250.7.111(rw,sync)
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;h5&gt;/etc/sysconfig/nfs&lt;/h5&gt;&lt;ac:structured-macro ac:macro-id="3da0d68e-4667-4eed-894d-96052926023d" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[#
# Define which protocol versions mountd
# will advertise. The values are "no" or "yes"
# with yes being the default
#MOUNTD_NFS_V1="no"
#MOUNTD_NFS_V2="no"
#MOUNTD_NFS_V3="no"
#
#
# Path to remote quota server. See rquotad(8)
#RQUOTAD="/usr/sbin/rpc.rquotad"
# Port rquotad should listen on.
RQUOTAD_PORT=4003
# Optinal options passed to rquotad
#RPCRQUOTADOPTS=""
#
# Optional arguments passed to in-kernel lockd
#LOCKDARG=
# TCP port rpc.lockd should listen on.
LOCKD_TCPPORT=4001
# UDP port rpc.lockd should listen on.
LOCKD_UDPPORT=4001
#
#
# Optional arguments passed to rpc.nfsd. See rpc.nfsd(8)
# Turn off v2 and v3 protocol support
#RPCNFSDARGS="-N 2 -N 3"
# Turn off v4 protocol support
#RPCNFSDARGS="-N 4"
# Number of nfs server processes to be started.
# The default is 8.
#RPCNFSDCOUNT=8
# Stop the nfsd module from being pre-loaded
#NFSD_MODULE="noload"
#
#
# Optional arguments passed to rpc.mountd. See rpc.mountd(8)
#RPCMOUNTDOPTS=""
# Port rpc.mountd should listen on.
MOUNTD_PORT=4002
#
#
# Optional arguments passed to rpc.statd. See rpc.statd(8)
#STATDARG=""
# Port rpc.statd should listen on.
STATD_PORT=4001
# Outgoing port statd should used. The default is port
# is random
STATD_OUTGOING_PORT=4004
# Specify callout program
#STATD_HA_CALLOUT="/usr/local/bin/foo"
#
#
# Optional arguments passed to rpc.idmapd. See rpc.idmapd(8)
#RPCIDMAPDARGS=""
#
# Set to turn on Secure NFS mounts.
#SECURE_NFS="yes"
# Optional arguments passed to rpc.gssd. See rpc.gssd(8)
#RPCGSSDARGS="-vvv"
# Optional arguments passed to rpc.svcgssd. See rpc.svcgssd(8)
#RPCSVCGSSDARGS="-vvv"
# Don't load security modules in to the kernel
#SECURE_NFS_MODS="noload"
#
# Don't load sunrpc module.
#RPCMTAB="noload"
#
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;h5&gt;/etc/hosts.allow&lt;/h5&gt;&lt;ac:structured-macro ac:macro-id="f3ec6a0a-d9f7-42b1-8a84-378d364ce844" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[portmap: 134.250.7.110, 134.250.7.111
lockd: 134.250.7.110, 134.250.7.111
rquotad: 134.250.7.110, 134.250.7.111
mountd: 134.250.7.110, 134.250.7.111
statd: 134.250.7.110, 134.250.7.111
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;h5&gt;/etc/hosts.deny&lt;/h5&gt;&lt;ac:structured-macro ac:macro-id="3a69eed4-bf24-4df4-9577-d3c70cf459c3" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[portmap:ALL
lockd:ALL
mountd:ALL
rquotad:ALL
statd:ALL
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;h3&gt;Troubleshooting&lt;/h3&gt;&lt;p&gt;If things aren't starting up as expected, try the following:&lt;/p&gt;&lt;ol&gt;&lt;li&gt;&amp;nbsp;Stop all services on the server:&lt;ol&gt;&lt;li&gt;service nfs stop&lt;/li&gt;&lt;li&gt;service nfslock stop&lt;/li&gt;&lt;li&gt;service portmap stop&lt;/li&gt;&lt;li&gt;service rpcsvcgssd stop&lt;/li&gt;&lt;li&gt;service rpcgssd stop&lt;/li&gt;&lt;li&gt;service rpcidmapd stop&lt;/li&gt;&lt;/ol&gt;&lt;/li&gt;&lt;li&gt;Start all services in the following order:&lt;ol&gt;&lt;li&gt;service portmap start&lt;/li&gt;&lt;li&gt;service nfslock start&lt;/li&gt;&lt;li&gt;service rpcsvcgssd start&lt;/li&gt;&lt;li&gt;service nfs restart&lt;/li&gt;&lt;/ol&gt;&lt;/li&gt;&lt;/ol&gt;</property>
    

<property name="body">h3. Server-side config files
h5. /etc/services
Append the following lines to the end of the file:
{code}
# Local services
rquotad         4003/tcp
rquotad         4003/udp
{code}</property>
    

<property name="body">h3. Server-side config files


h5. /etc/services

Append the following lines to the end of the file:
{code}
# Local services
rquotad         4003/tcp
rquotad         4003/udp
{code}

h5. /etc/exports
{code}
/usr/local/jobout 134.250.5.0/24(rw,sync)
{code}</property>
    

<property name="body">h3. Server-side config files


h5. /etc/services

Append the following lines to the end of the file:
{code}
# Local services
rquotad         4003/tcp
rquotad         4003/udp
{code}

h5. /etc/exports
{code}
/usr/local/jobout 134.250.5.0/24(rw,sync)
{code}

h5. /etc/sysconfig/nfs
{code}
#
# Define which protocol versions mountd
# will advertise. The values are "no" or "yes"
# with yes being the default
#MOUNTD_NFS_V1="no"
#MOUNTD_NFS_V2="no"
#MOUNTD_NFS_V3="no"
#
#
# Path to remote quota server. See rquotad(8)
#RQUOTAD="/usr/sbin/rpc.rquotad"
# Port rquotad should listen on.
RQUOTAD_PORT=4003
# Optinal options passed to rquotad
#RPCRQUOTADOPTS=""
#
# Optional arguments passed to in-kernel lockd
#LOCKDARG=
# TCP port rpc.lockd should listen on.
LOCKD_TCPPORT=4001
# UDP port rpc.lockd should listen on.
LOCKD_UDPPORT=4001
#
#
# Optional arguments passed to rpc.nfsd. See rpc.nfsd(8)
# Turn off v2 and v3 protocol support
#RPCNFSDARGS="-N 2 -N 3"
# Turn off v4 protocol support
#RPCNFSDARGS="-N 4"
# Number of nfs server processes to be started.
# The default is 8.
#RPCNFSDCOUNT=8
# Stop the nfsd module from being pre-loaded
#NFSD_MODULE="noload"
#
#
# Optional arguments passed to rpc.mountd. See rpc.mountd(8)
#RPCMOUNTDOPTS=""
# Port rpc.mountd should listen on.
MOUNTD_PORT=4002
#
#
# Optional arguments passed to rpc.statd. See rpc.statd(8)
#STATDARG=""
# Port rpc.statd should listen on.
STATD_PORT=4001
# Outgoing port statd should used. The default is port
# is random
STATD_OUTGOING_PORT=4004
# Specify callout program
#STATD_HA_CALLOUT="/usr/local/bin/foo"
#
#
# Optional arguments passed to rpc.idmapd. See rpc.idmapd(8)
#RPCIDMAPDARGS=""
#
# Set to turn on Secure NFS mounts.
#SECURE_NFS="yes"
# Optional arguments passed to rpc.gssd. See rpc.gssd(8)
#RPCGSSDARGS="-vvv"
# Optional arguments passed to rpc.svcgssd. See rpc.svcgssd(8)
#RPCSVCGSSDARGS="-vvv"
# Don't load security modules in to the kernel
#SECURE_NFS_MODS="noload"
#
# Don't load sunrpc module.
#RPCMTAB="noload"
#
{code}</property>
    

<property name="body">h3. Server-side config files


h5. /etc/services

Append the following lines to the end of the file:
{code}
# Local services
rquotad         4003/tcp
rquotad         4003/udp
{code}

h5. /etc/exports
{code}
/usr/local/jobout 134.250.5.0/24(rw,sync)
{code}

h5. /etc/sysconfig/nfs
{code}
#
# Define which protocol versions mountd
# will advertise. The values are "no" or "yes"
# with yes being the default
#MOUNTD_NFS_V1="no"
#MOUNTD_NFS_V2="no"
#MOUNTD_NFS_V3="no"
#
#
# Path to remote quota server. See rquotad(8)
#RQUOTAD="/usr/sbin/rpc.rquotad"
# Port rquotad should listen on.
RQUOTAD_PORT=4003
# Optinal options passed to rquotad
#RPCRQUOTADOPTS=""
#
# Optional arguments passed to in-kernel lockd
#LOCKDARG=
# TCP port rpc.lockd should listen on.
LOCKD_TCPPORT=4001
# UDP port rpc.lockd should listen on.
LOCKD_UDPPORT=4001
#
#
# Optional arguments passed to rpc.nfsd. See rpc.nfsd(8)
# Turn off v2 and v3 protocol support
#RPCNFSDARGS="-N 2 -N 3"
# Turn off v4 protocol support
#RPCNFSDARGS="-N 4"
# Number of nfs server processes to be started.
# The default is 8.
#RPCNFSDCOUNT=8
# Stop the nfsd module from being pre-loaded
#NFSD_MODULE="noload"
#
#
# Optional arguments passed to rpc.mountd. See rpc.mountd(8)
#RPCMOUNTDOPTS=""
# Port rpc.mountd should listen on.
MOUNTD_PORT=4002
#
#
# Optional arguments passed to rpc.statd. See rpc.statd(8)
#STATDARG=""
# Port rpc.statd should listen on.
STATD_PORT=4001
# Outgoing port statd should used. The default is port
# is random
STATD_OUTGOING_PORT=4004
# Specify callout program
#STATD_HA_CALLOUT="/usr/local/bin/foo"
#
#
# Optional arguments passed to rpc.idmapd. See rpc.idmapd(8)
#RPCIDMAPDARGS=""
#
# Set to turn on Secure NFS mounts.
#SECURE_NFS="yes"
# Optional arguments passed to rpc.gssd. See rpc.gssd(8)
#RPCGSSDARGS="-vvv"
# Optional arguments passed to rpc.svcgssd. See rpc.svcgssd(8)
#RPCSVCGSSDARGS="-vvv"
# Don't load security modules in to the kernel
#SECURE_NFS_MODS="noload"
#
# Don't load sunrpc module.
#RPCMTAB="noload"
#
{code}

h5. /etc/hosts.allow
{code}
portmap: 134.250.5.0/24
lockd: 134.250.5.0/24
rquotad: 134.250.5.0/24
mountd: 134.250.5.0/24
statd: 134.250.5.0/24
{code}</property>
    

<property name="body">h3. Server-side config files


h5. /etc/services

Append the following lines to the end of the file:
{code}
# Local services
rquotad         4003/tcp
rquotad         4003/udp
{code}

h5. /etc/exports
{code}
/usr/local/jobout 134.250.5.0/24(rw,sync)
{code}

h5. /etc/sysconfig/nfs
{code}
#
# Define which protocol versions mountd
# will advertise. The values are "no" or "yes"
# with yes being the default
#MOUNTD_NFS_V1="no"
#MOUNTD_NFS_V2="no"
#MOUNTD_NFS_V3="no"
#
#
# Path to remote quota server. See rquotad(8)
#RQUOTAD="/usr/sbin/rpc.rquotad"
# Port rquotad should listen on.
RQUOTAD_PORT=4003
# Optinal options passed to rquotad
#RPCRQUOTADOPTS=""
#
# Optional arguments passed to in-kernel lockd
#LOCKDARG=
# TCP port rpc.lockd should listen on.
LOCKD_TCPPORT=4001
# UDP port rpc.lockd should listen on.
LOCKD_UDPPORT=4001
#
#
# Optional arguments passed to rpc.nfsd. See rpc.nfsd(8)
# Turn off v2 and v3 protocol support
#RPCNFSDARGS="-N 2 -N 3"
# Turn off v4 protocol support
#RPCNFSDARGS="-N 4"
# Number of nfs server processes to be started.
# The default is 8.
#RPCNFSDCOUNT=8
# Stop the nfsd module from being pre-loaded
#NFSD_MODULE="noload"
#
#
# Optional arguments passed to rpc.mountd. See rpc.mountd(8)
#RPCMOUNTDOPTS=""
# Port rpc.mountd should listen on.
MOUNTD_PORT=4002
#
#
# Optional arguments passed to rpc.statd. See rpc.statd(8)
#STATDARG=""
# Port rpc.statd should listen on.
STATD_PORT=4001
# Outgoing port statd should used. The default is port
# is random
STATD_OUTGOING_PORT=4004
# Specify callout program
#STATD_HA_CALLOUT="/usr/local/bin/foo"
#
#
# Optional arguments passed to rpc.idmapd. See rpc.idmapd(8)
#RPCIDMAPDARGS=""
#
# Set to turn on Secure NFS mounts.
#SECURE_NFS="yes"
# Optional arguments passed to rpc.gssd. See rpc.gssd(8)
#RPCGSSDARGS="-vvv"
# Optional arguments passed to rpc.svcgssd. See rpc.svcgssd(8)
#RPCSVCGSSDARGS="-vvv"
# Don't load security modules in to the kernel
#SECURE_NFS_MODS="noload"
#
# Don't load sunrpc module.
#RPCMTAB="noload"
#
{code}

h5. /etc/hosts.allow
{code}
portmap: 134.250.5.0/24
lockd: 134.250.5.0/24
rquotad: 134.250.5.0/24
mountd: 134.250.5.0/24
statd: 134.250.5.0/24
{code}

h5. /etc/hosts.deny
{code}
portmap:ALL
lockd:ALL
mountd:ALL
rquotad:ALL
statd:ALL
{code}</property>
    

<property name="body">h3. Server-side config files


h5. /etc/services

Append the following lines to the end of the file:
{code}
# Local services
rquotad         4003/tcp
rquotad         4003/udp
{code}

h5. /etc/exports
{code}
/usr/local/jobout 134.250.7.110(rw,sync) 134.250.7.111(rw,sync)
{code}

h5. /etc/sysconfig/nfs
{code}
#
# Define which protocol versions mountd
# will advertise. The values are "no" or "yes"
# with yes being the default
#MOUNTD_NFS_V1="no"
#MOUNTD_NFS_V2="no"
#MOUNTD_NFS_V3="no"
#
#
# Path to remote quota server. See rquotad(8)
#RQUOTAD="/usr/sbin/rpc.rquotad"
# Port rquotad should listen on.
RQUOTAD_PORT=4003
# Optinal options passed to rquotad
#RPCRQUOTADOPTS=""
#
# Optional arguments passed to in-kernel lockd
#LOCKDARG=
# TCP port rpc.lockd should listen on.
LOCKD_TCPPORT=4001
# UDP port rpc.lockd should listen on.
LOCKD_UDPPORT=4001
#
#
# Optional arguments passed to rpc.nfsd. See rpc.nfsd(8)
# Turn off v2 and v3 protocol support
#RPCNFSDARGS="-N 2 -N 3"
# Turn off v4 protocol support
#RPCNFSDARGS="-N 4"
# Number of nfs server processes to be started.
# The default is 8.
#RPCNFSDCOUNT=8
# Stop the nfsd module from being pre-loaded
#NFSD_MODULE="noload"
#
#
# Optional arguments passed to rpc.mountd. See rpc.mountd(8)
#RPCMOUNTDOPTS=""
# Port rpc.mountd should listen on.
MOUNTD_PORT=4002
#
#
# Optional arguments passed to rpc.statd. See rpc.statd(8)
#STATDARG=""
# Port rpc.statd should listen on.
STATD_PORT=4001
# Outgoing port statd should used. The default is port
# is random
STATD_OUTGOING_PORT=4004
# Specify callout program
#STATD_HA_CALLOUT="/usr/local/bin/foo"
#
#
# Optional arguments passed to rpc.idmapd. See rpc.idmapd(8)
#RPCIDMAPDARGS=""
#
# Set to turn on Secure NFS mounts.
#SECURE_NFS="yes"
# Optional arguments passed to rpc.gssd. See rpc.gssd(8)
#RPCGSSDARGS="-vvv"
# Optional arguments passed to rpc.svcgssd. See rpc.svcgssd(8)
#RPCSVCGSSDARGS="-vvv"
# Don't load security modules in to the kernel
#SECURE_NFS_MODS="noload"
#
# Don't load sunrpc module.
#RPCMTAB="noload"
#
{code}

h5. /etc/hosts.allow
{code}
portmap: 134.250.5.0/24
lockd: 134.250.5.0/24
rquotad: 134.250.5.0/24
mountd: 134.250.5.0/24
statd: 134.250.5.0/24
{code}

h5. /etc/hosts.deny
{code}
portmap:ALL
lockd:ALL
mountd:ALL
rquotad:ALL
statd:ALL
{code}</property>
    

<property name="body">{code}
SErvername  tivoli
   COMMmethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu

nodename BIRCHINB 
passwordaccess generate
MANAGEDSERVICES	schedule webclient
include /u01/.../*
include /home/.../*
include /etc/.../*
include /root/.../*
exclude.dir /bin
exclude.dir /boot
exclude.dir /boot/grub
exclude.dir /boot/lost+found
exclude.dir /dev
exclude.dir /initrd
exclude.dir /lib
exclude.dir /lib/lsb
exclude.dir /lib/modules
exclude.dir /lib/rtkaio
exclude.dir /lib/security
exclude.dir /lib/udev
exclude.dir /lost+found
exclude.dir /media
exclude.dir /misc
exclude.dir /mnt
exclude.dir /opt
exclude.dir /proc
exclude.dir /root
exclude.dir /sbin
exclude.dir /srv
exclude.dir /selinux
exclude.dir /sys
exclude.dir /tftpboot
exclude.dir /tmp
exclude.dir /var
exclude.dir /usr
{code}</property>
    

<property name="body">h4. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}

h2. Example dsm.sys file - Ubuntu Server 64-bit
{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMMethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu
nodename WIKI
passwordaccess generate
MANAGEDSERVICES schedule webclient
virtualmountpoint /
virtualmountpoint /home
virtualmountpoint /etc
include /home/.../*
include /etc/.../*
exclude.dir /dev
exclude.dir /mnt
exclude.dir /proc
{code}

h2. Example dsm.sys for Red Hat servers
{code}
SErvername  tivoli
   COMMmethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu

nodename BIRCHINB 
passwordaccess generate
MANAGEDSERVICES	schedule webclient
include /u01/.../*
include /home/.../*
include /etc/.../*
include /root/.../*
exclude.dir /dev
exclude.dir /mnt
exclude.dir /opt
exclude.dir /proc
{code}

h2. Configuring Automatic Startup
Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
#export LANG=en_US;
#export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
FOR UBUNTU SERVER:

chmod 755 suu_tivoli
update-rc.d suu_tivoli defaults

FOR RED HAT:
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc
It will prompt you for your nodename and password.  Once you have entered them, it will drop you at a tsm&gt; prompt.
You can then type 'backup', no quotes, and it will start an incremental backup.  If you don't want to start one right away,
just type 'quit', no quotes, and it will drop you back at the linux prompt.
To start the daemon, run the following command:

#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Server Notes

{code}
Installing TSM Client V5.5.2 on Ubuntu 9.04 Server 64-bit

Note: These instructions are based on the report "TSM-Client unter Debian/etch einrichten" at "https://wiki.gw.dg.de/index.php/TSM:debian"



1) get the latest client - modify version numbers as needed
wget "ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v5r5/Linux/LinuxX86/v553/5.5.3.0-TIV-TSMBAC-LinuxX86.tar"

** NOTE - execute "sudo su -" prior to running the following build and install.  Otherwise, permissions get jacked

2) apt-get install alien ksh ia32-libs gawk

3) unpack the archive
tar xvf 5.5.3.0-TIV-TSMBAC-LinuxX86.tar

4) unpack the RPM archives (ignore warnings re scripts)
alien -g TIVsm-API.i386.rpm
alien -g TIVsm-BA.i386.rpm

5) change directory names
mv TIVsm-API-5.5.3/debian TIVsm-API-5.5.3/DEBIAN
mv TIVsm-BA-5.5.3/debian TIVsm-BA-5.5.3/DEBIAN

6) edit the control files

vi TIVsm-API-5.5.3/DEBIAN/control
Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-api
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-api
Architecture: amd64
Depends:
Description: the API IBM Tivoli Storage Manager API
Version: 5.5.3
&lt;blank line&gt;

Save and exit the file.

vi TIVsm-BA-5.5.3/DEBIAN/control

Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-ba
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-ba
Architecture: amd64
Depends:
Description: the Backup Archive Client IBM Tivoli Storage Manager Client
Version: 5.5.3
&lt;blank line&gt;

Save and exit the file

7) create *.deb packages
dpkg -b TIVsm-API-5.5.3
dpkg -b TIVsm-BA-5.5.3

8) install *.deb packages
dpkg -i TIVsm-API-5.5.3.deb
dpkg -i TIVsm-BA-5.5.3.deb

9)
cd /tmp
wget [http://security.ubuntu.com/ubuntu/pool/universe/i/ia32-libs/ia32-libs_20090808ubuntu9_amd64.deb]
dpkg-deb \-x ia32-libs_20090808ubuntu9_amd64.deb ia32-libs
sudo cp ia32-libs/usr/lib32/libstdc++.so.5.0.7 /usr/lib32/
cd /usr/lib32
sudo ln \-s libstdc\++.so.5.0.7 libstdc+\+.so.5
10) create/modify TSM configuration files
 (use examples listed above)
vi /opt/tivoli/tsm/client/ba/bin/dsm.opt
vi /opt/tivoli/tsm/client/ba/bin/dsm.sys

11) Run the "Error loading shared libraries" fix located above; run the "English message repository not found" fix as well

12) Link the necessary shared libraries:
add the dsm binary path on a line in the file /etc/ld.so.conf
/opt/tivoli/tsm/client/api/bin
import the shared objects using the command
ldconfig
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/EN_US/

13) run an incremental backup
dsmc incremental

14) start the TSM scheduler
#/etc/init.d/suu_tivoli start
{code}</property>
    

<property name="body">h3. Create log4j.properties file
Create a log4j.properties file in the $CATALINA_HOME/lib directory with the following contents (modify file size as desired):
{code}
log4j.rootLogger=INFO, R 
log4j.appender.R=org.apache.log4j.RollingFileAppender 
log4j.appender.R.File=${catalina.base}/logs/tomcat.log 
log4j.appender.R.MaxFileSize=10MB 
log4j.appender.R.MaxBackupIndex=10 
log4j.appender.R.layout=org.apache.log4j.PatternLayout 
log4j.appender.R.layout.ConversionPattern=%p %t %c - %m%n
{code}

h3. Download JAR files
Obtain a copy of all JAR files from the sherpa server under Tomcat\log4j folder

h3. Stop Tomcat, place JARs in directories
Stop Tomcat

Place the log4j-1.2.x.jar in $CATALINA_HOME/lib.
Replace $CATALINA_HOME/bin/tomcat-juli.jar with downloaded tomcat-juli.jar
Place downloaded tomcat-juli-adapters.jar in $CATALINA_HOME/lib
Delete $CATALINA_BASE/conf/logging.properties to prevent java.util.logging generating zero length log files

Start Tomcat</property>
    

<property name="body">h3. Create log4j.properties file

Create a log4j.properties file in the $CATALINA_HOME/lib directory with the following contents (modify file size as desired):
{code}
log4j.rootLogger=WARN, CATALINA

# Define all the appenders
log4j.appender.CATALINA=org.apache.log4j.RollingFileAppender
log4j.appender.CATALINA.file=${catalina.base}/logs/catalina.log
log4j.appender.CATALINA.MaxFileSize=50MB
log4j.appender.CATALINA.MaxBackupIndex=200
log4j.appender.CATALINA.layout=org.apache.log4j.PatternLayout
log4j.appender.CATALINA.append=true
log4j.rootCategory=ALL, CATALINA
{code}

h3. Download JAR files

Obtain a copy of all JAR files from the sherpa server under Tomcat\log4j folder

h3. Stop Tomcat, place JARs in directories

Stop Tomcat

Place the log4j-1.2.x.jar in $CATALINA_HOME/lib.
Replace $CATALINA_HOME/bin/tomcat-juli.jar with downloaded tomcat-juli.jar
Place downloaded tomcat-juli-adapters.jar in $CATALINA_HOME/lib
Delete $CATALINA_BASE/conf/logging.properties to prevent java.util.logging generating zero length log files

Start Tomcat</property>
    

<property name="body">&lt;h4&gt;/&amp;lt;tomcat_home&amp;gt;/conf/Catalina/localhost/manager.xml&lt;/h4&gt;
&lt;ac:structured-macro ac:macro-id="9ea25fab-b81b-403a-972b-10071903b1b9" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0?

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
--&gt;
&lt;!--

Context configuration file for the Tomcat Manager Web App

$Id: manager.xml 562814 2007-08-05 03:52:04Z markt $

--&gt;

&lt;Context docBase="${catalina.home}/webapps/manager" privileged="true" antiResourceLocking="false" antiJARLocking="false"&gt;
&lt;Valve className="org.apache.catalina.valves.RemoteAddrValve" allow="127.0.0.1,134.250.4.*"/&gt;
&lt;/Context&gt;
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;

&lt;h4&gt;/&amp;lt;tomcat_home&amp;gt;/conf/server.xml&lt;/h4&gt;
&lt;ac:structured-macro ac:macro-id="041d869e-1840-4aa7-8e18-34b92b65dab8" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
&lt;?xml version='1.0' encoding='utf-8'?&gt;
&lt;!--
  Licensed to the Apache Software Foundation (ASF) under one or more
  contributor license agreements.  See the NOTICE file distributed with
  this work for additional information regarding copyright ownership.
  The ASF licenses this file to You under the Apache License, Version 2.0
  (the "License"); you may not use this file except in compliance with
  the License.  You may obtain a copy of the License at

      http://www.apache.org/licenses/LICENSE-2.0

  Unless required by applicable law or agreed to in writing, software
  distributed under the License is distributed on an "AS IS" BASIS,
  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  See the License for the specific language governing permissions and
  limitations under the License.
--&gt;
&lt;!-- Note:  A "Server" is not itself a "Container", so you may not
     define subcomponents such as "Valves" at this level.
     Documentation at /docs/config/server.html
 --&gt;
&lt;Server port="8005" shutdown="SHUTDOWN"&gt;

  &lt;!--APR library loader. Documentation at /docs/apr.html --&gt;
  &lt;Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" /&gt;
  &lt;!--Initialize Jasper prior to webapps are loaded. Documentation at /docs/jasper-howto.html --&gt;
  &lt;Listener className="org.apache.catalina.core.JasperListener" /&gt;
  &lt;!-- JMX Support for the Tomcat server. Documentation at /docs/non-existent.html --&gt;
  &lt;Listener className="org.apache.catalina.mbeans.ServerLifecycleListener" /&gt;
  &lt;Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" /&gt;

  &lt;!-- Global JNDI resources
       Documentation at /docs/jndi-resources-howto.html
  --&gt;
  &lt;GlobalNamingResources&gt;
    &lt;!-- Editable user database that can also be used by
         UserDatabaseRealm to authenticate users
    --&gt;
    &lt;Resource name="UserDatabase" auth="Container"
              type="org.apache.catalina.UserDatabase"
              description="User database that can be updated and saved"
              factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
              pathname="conf/tomcat-users.xml" /&gt;
  &lt;/GlobalNamingResources&gt;

  &lt;!-- A "Service" is a collection of one or more "Connectors" that share
       a single "Container" Note:  A "Service" is not itself a "Container",
       so you may not define subcomponents such as "Valves" at this level.
       Documentation at /docs/config/service.html
   --&gt;
  &lt;Service name="Catalina"&gt;

    &lt;!--The connectors can use a shared executor, you can define one or more named thread pools--&gt;
    &lt;!--
    &lt;Executor name="tomcatThreadPool" namePrefix="catalina-exec-"
        maxThreads="150" minSpareThreads="4"/&gt;
    --&gt;


    &lt;!-- A "Connector" represents an endpoint by which requests are received
         and responses are returned. Documentation at :
         Java HTTP Connector: /docs/config/http.html (blocking &amp; non-blocking)
         Java AJP  Connector: /docs/config/ajp.html
         APR (HTTP/AJP) Connector: /docs/apr.html
         Define a non-SSL HTTP/1.1 Connector on port 8080
    --&gt;
  &lt;!-- &lt;Connector port="8080" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443" /&gt;  --&gt;
    &lt;!-- A "Connector" using the shared thread pool--&gt;
    &lt;!--
    &lt;Connector executor="tomcatThreadPool"
               port="8080" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443" /&gt;
    --&gt;
    &lt;!-- Define a SSL HTTP/1.1 Connector on port 8443
         This connector uses the JSSE configuration, when using APR, the
         connector should be using the OpenSSL style configuration
         described in the APR documentation --&gt;

    &lt;Connector  port="8443"
                protocol="org.apache.coyote.http11.Http11Protocol"
                ciphers="SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA"
              SSLEnabled="true"
                enableLookups="false"
                disableUploadTimeout="true"
                acceptCount="100"
                maxThreads="200"
                scheme="https"
                secure="true"
                clientAuth="false"
                keystoreFile="/home/touchnet/ssl/keystore.wc"
                keystorePass="&lt;removedforwiki&gt;"
                sslProtocol="TLS"
      /&gt;

    &lt;!-- Define an AJP 1.3 Connector on port 8009 --&gt;
    &lt;Connector port="8009" protocol="AJP/1.3" redirectPort="8443" /&gt;


    &lt;!-- An Engine represents the entry point (within Catalina) that processes
         every request.  The Engine implementation for Tomcat stand alone
         analyzes the HTTP headers included with the request, and passes them
         on to the appropriate Host (virtual host).
         Documentation at /docs/config/engine.html --&gt;

    &lt;!-- You should set jvmRoute to support load-balancing via AJP ie :
    &lt;Engine name="Catalina" defaultHost="localhost" jvmRoute="jvm1"&gt;
    --&gt;
    &lt;Engine name="Catalina" defaultHost="localhost"&gt;

      &lt;!--For clustering, please take a look at documentation at:
          /docs/cluster-howto.html  (simple how to)
          /docs/config/cluster.html (reference documentation) --&gt;
      &lt;!--
      &lt;Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster"/&gt;
      --&gt;

      &lt;!-- The request dumper valve dumps useful debugging information about
           the request and response data received and sent by Tomcat.
           Documentation at: /docs/config/valve.html --&gt;
      &lt;!--
      &lt;Valve className="org.apache.catalina.valves.RequestDumperValve"/&gt;
      --&gt;

      &lt;!-- This Realm uses the UserDatabase configured in the global JNDI
           resources under the key "UserDatabase".  Any edits
           that are performed against this UserDatabase are immediately
           available for use by the Realm.  --&gt;
      &lt;Realm className="org.apache.catalina.realm.UserDatabaseRealm"
             resourceName="UserDatabase" digest="SHA" /&gt;

      &lt;!-- Define the default virtual host
           Note: XML Schema validation will not work with Xerces 2.2.
       --&gt;
      &lt;Host name="localhost"  appBase="webapps"
            unpackWARs="true" autoDeploy="true"
            xmlValidation="false" xmlNamespaceAware="false"&gt;

        &lt;!-- SingleSignOn valve, share authentication between web applications
             Documentation at: /docs/config/valve.html --&gt;
        &lt;!--
        &lt;Valve className="org.apache.catalina.authenticator.SingleSignOn" /&gt;
        --&gt;

        &lt;!-- Access log processes all example.
             Documentation at: /docs/config/valve.html --&gt;
        &lt;!--
        &lt;Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"
               prefix="localhost_access_log." suffix=".txt" pattern="common" resolveHosts="false"/&gt;
        --&gt;

      &lt;/Host&gt;
    &lt;/Engine&gt;
  &lt;/Service&gt;
&lt;/Server&gt;
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;

&lt;h4&gt;/&amp;lt;tomcat_home&amp;gt;/conf/logging.properties&lt;/h4&gt;
&lt;ac:structured-macro ac:macro-id="4737066f-71ed-4521-af71-08b10ac21359" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
# Licensed to the Apache Software Foundation (ASF) under one or more
# contributor license agreements.  See the NOTICE file distributed with
# this work for additional information regarding copyright ownership.
# The ASF licenses this file to You under the Apache License, Version 2.0
# (the "License"); you may not use this file except in compliance with
# the License.  You may obtain a copy of the License at
#
#     http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

handlers = 1catalina.org.apache.juli.FileHandler, 2localhost.org.apache.juli.FileHandler, 3manager.org.apache.juli.FileHandler, 4host-manager.org.apache.juli.FileHandler, java.util.logging.ConsoleHandler

.handlers = 1catalina.org.apache.juli.FileHandler, java.util.logging.ConsoleHandler

############################################################
# Handler specific properties.
# Describes specific configuration info for Handlers.
############################################################

1catalina.org.apache.juli.FileHandler.level = WARNING
1catalina.org.apache.juli.FileHandler.directory = ${catalina.base}/logs
1catalina.org.apache.juli.FileHandler.prefix = catalina.

2localhost.org.apache.juli.FileHandler.level = WARNING
2localhost.org.apache.juli.FileHandler.directory = ${catalina.base}/logs
2localhost.org.apache.juli.FileHandler.prefix = localhost.

3manager.org.apache.juli.FileHandler.level = WARNING
3manager.org.apache.juli.FileHandler.directory = ${catalina.base}/logs
3manager.org.apache.juli.FileHandler.prefix = manager.

4host-manager.org.apache.juli.FileHandler.level = WARNING
4host-manager.org.apache.juli.FileHandler.directory = ${catalina.base}/logs
4host-manager.org.apache.juli.FileHandler.prefix = host-manager.

java.util.logging.ConsoleHandler.level = WARNING
java.util.logging.ConsoleHandler.formatter = java.util.logging.SimpleFormatter


############################################################
# Facility specific properties.
# Provides extra control for each logger.
############################################################

org.apache.catalina.core.ContainerBase.[Catalina].[localhost].level = WARNING
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].handlers = 2localhost.org.apache.juli.FileHandler

org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/manager].level = WARNING
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/manager].handlers = 3manager.org.apache.juli.FileHandler

org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/host-manager].level = WARNING
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/host-manager].handlers = 4host-manager.org.apache.juli.FileHandler

# For example, set the com.xyz.foo logger to only log SEVERE
# messages:
#org.apache.catalina.startup.ContextConfig.level = WARNING
#org.apache.catalina.startup.HostConfig.level = WARNING
#org.apache.catalina.session.ManagerBase.level = WARNING
#org.apache.catalina.core.AprLifecycleListener.level=WARNING
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;</property>
    

<property name="body">h4. /&lt;tomcat_home&gt;/conf/Catalina/localhost/manager.xml
{code}
&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0?

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
--&gt;
&lt;!--

Context configuration file for the Tomcat Manager Web App

$Id: manager.xml 562814 2007-08-05 03:52:04Z markt $

--&gt;

&lt;Context docBase="${catalina.home}/webapps/manager" privileged="true" antiResourceLocking="false" antiJARLocking="false"&gt;
&lt;Valve className="org.apache.catalina.valves.RemoteAddrValve" allow="127.0.0.1,134.250.4.*"/&gt;
&lt;/Context&gt;
&lt;code&gt;</property>
    

<property name="body">&lt;h4&gt;Populate /etc/init.d/suu_tomcat&lt;/h4&gt;
&lt;ac:structured-macro ac:macro-id="c628c78a-0c40-4901-9580-3d576bfce11f" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
#!/bin/bash
#
# Startup script for Tomcat server
#
# chkconfig: - 83 53
# description: Starts and stops the Tomcat daemon.
# processname: tomcat
# pidfile: /var/run/tomcat.pid
export JAVA_HOME=/usr/lib/jvm/java-6-sun
export TOMCAT_HOME=&lt;tomcat_home_dir&gt;
export TOMCAT_USER=&lt;tomcat user&gt;

# See how we were called.
case $1 in
        start)

su - $TOMCAT_USER -c "sh $TOMCAT_HOME/bin/startup.sh"
        ;;
        stop)
su - $TOMCAT_USER -c "sh $TOMCAT_HOME/bin/shutdown.sh"
        ;;
        restart)
su - $TOMCAT_USER -c "sh $TOMCAT_HOME/bin/shutdown.sh"
su - $TOMCAT_USER -c "sh $TOMCAT_HOME/bin/startup.sh"
        ;;
        *)
                echo "Usage: /etc/init.d/suu_tomcat start|stop|restart"
        ;;
esac

exit 0
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;

&lt;p&gt;A couple of things to note here; we 'su' to the user we want the process to run as. This is important because we do NOT want processes running as root. Additionally, we are explicitly setting the JAVA_HOME environment variable here, but you may wish to set it in /etc/profile (system-wide) or ~.bashrc (user-specific).&lt;/p&gt;

&lt;h4&gt;Set for automatic startup&lt;/h4&gt;
&lt;p&gt;Run the following as root  (Ubuntu and Red Hat):&lt;/p&gt;
&lt;ac:structured-macro ac:macro-id="e4ff15dc-8cf6-4cea-9f72-7b5648188ec7" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
chmod 755 /etc/init.d/suu_tomcat
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;
&lt;p&gt;Next, run the following as root:&lt;br /&gt;
For Red Hat:&lt;/p&gt;
&lt;ac:structured-macro ac:macro-id="c51918e2-f9ea-40f3-a082-ab9ea558735f" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
chkconfig --add suu_tomcat
chkconfig --level 345 suu_tomcat on
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;

&lt;p&gt;For Ubuntu:&lt;/p&gt;
&lt;ac:structured-macro ac:macro-id="bfd79648-ffc0-4031-b2b9-8e621b8e1ebc" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
update-rc.d suu_tomcat defaults
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;

&lt;p&gt;That's it - reboot and make sure it works.&lt;/p&gt;</property>
    

<property name="body">h4. /etc/init.d/suu_tomcat
{code}
#!/bin/bash
#
# Startup script for Tomcat server
#
# chkconfig: - 83 53
# description: Starts and stops the Tomcat daemon.
# processname: tomcat
# pidfile: /var/run/tomcat.pid
export JAVA_HOME=/usr/lib/jvm/java-6-sun
export TOMCAT_HOME=/home/billservice/apps/apache-tomcat-6.0.18
export TOMCAT_USER=billservice

# See how we were called.
case $1 in
        start)

su - $TOMCAT_USER -c "sh $TOMCAT_HOME/bin/startup.sh"
        ;;
        stop)
su - $TOMCAT_USER -c "sh $TOMCAT_HOME/bin/shutdown.sh"
        ;;
        restart)
su - $TOMCAT_USER -c "sh $TOMCAT_HOME/bin/shutdown.sh"
su - $TOMCAT_USER -c "sh $TOMCAT_HOME/bin/startup.sh"
        ;;
        *)
                echo "Usage: /etc/init.d/tomcat start|stop|restart"
        ;;
esac

exit 0
{code}

A couple of things to note here; we 'su' to the user we want the process to run as. This is important because we do NOT want processes running as root. Additionally, we are explicitly setting the JAVA_HOME environment variable here, but you may wish to set it in /etc/profile (system-wide) or ~.bashrc (user-specific).</property>
    

<property name="body">h4. /etc/init.d/suu_tomcat
{code}
#!/bin/bash
#
# Startup script for Tomcat server
#
# chkconfig: - 83 53
# description: Starts and stops the Tomcat daemon.
# processname: tomcat
# pidfile: /var/run/tomcat.pid
export JAVA_HOME=/usr/lib/jvm/java-6-sun
export TOMCAT_HOME=&lt;tomcat_home_dir&gt;
export TOMCAT_USER=&lt;tomcat user&gt;

# See how we were called.
case $1 in
        start)

su - $TOMCAT_USER -c "sh $TOMCAT_HOME/bin/startup.sh"
        ;;
        stop)
su - $TOMCAT_USER -c "sh $TOMCAT_HOME/bin/shutdown.sh"
        ;;
        restart)
su - $TOMCAT_USER -c "sh $TOMCAT_HOME/bin/shutdown.sh"
su - $TOMCAT_USER -c "sh $TOMCAT_HOME/bin/startup.sh"
        ;;
        *)
                echo "Usage: /etc/init.d/suu_tomcat start|stop|restart"
        ;;
esac

exit 0
{code}

A couple of things to note here; we 'su' to the user we want the process to run as. This is important because we do NOT want processes running as root. Additionally, we are explicitly setting the JAVA_HOME environment variable here, but you may wish to set it in /etc/profile (system-wide) or \~.bashrc (user-specific).</property>
    

<property name="body">h4. /&lt;tomcat_home&gt;/conf/Catalina/localhost/manager.xml
{code}
&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0?

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
--&gt;
&lt;!--

Context configuration file for the Tomcat Manager Web App

$Id: manager.xml 562814 2007-08-05 03:52:04Z markt $

--&gt;

&lt;Context docBase="${catalina.home}/webapps/manager" privileged="true" antiResourceLocking="false" antiJARLocking="false"&gt;
&lt;Valve className="org.apache.catalina.valves.RemoteAddrValve" allow="127.0.0.1,134.250.4.*"/&gt;
&lt;/Context&gt;
{code}</property>
    

<property name="body">h4. /&lt;tomcat_home&gt;/conf/Catalina/localhost/manager.xml
{code}
&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0?

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
--&gt;
&lt;!--

Context configuration file for the Tomcat Manager Web App

$Id: manager.xml 562814 2007-08-05 03:52:04Z markt $

--&gt;

&lt;Context docBase="${catalina.home}/webapps/manager" privileged="true" antiResourceLocking="false" antiJARLocking="false"&gt;
&lt;Valve className="org.apache.catalina.valves.RemoteAddrValve" allow="127.0.0.1,134.250.4.*"/&gt;
&lt;/Context&gt;
{code}

h4. /&lt;tomcat_home&gt;/conf/server.xml
{code}
&lt;?xml version='1.0' encoding='utf-8'?&gt;
&lt;!--
  Licensed to the Apache Software Foundation (ASF) under one or more
  contributor license agreements.  See the NOTICE file distributed with
  this work for additional information regarding copyright ownership.
  The ASF licenses this file to You under the Apache License, Version 2.0
  (the "License"); you may not use this file except in compliance with
  the License.  You may obtain a copy of the License at

      http://www.apache.org/licenses/LICENSE-2.0

  Unless required by applicable law or agreed to in writing, software
  distributed under the License is distributed on an "AS IS" BASIS,
  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  See the License for the specific language governing permissions and
  limitations under the License.
--&gt;
&lt;tomcat-users&gt;
  &lt;role rolename="manager"/&gt;
  &lt;user username="tomcatadmin" password="058886b788d1f52e070e3bbb398b4335d8044fb9" roles="manager" /&gt;
&lt;/tomcat-users&gt;
root@store:/home/touchnet/Tomcat/conf# cat server.xml
&lt;?xml version='1.0' encoding='utf-8'?&gt;
&lt;!--
  Licensed to the Apache Software Foundation (ASF) under one or more
  contributor license agreements.  See the NOTICE file distributed with
  this work for additional information regarding copyright ownership.
  The ASF licenses this file to You under the Apache License, Version 2.0
  (the "License"); you may not use this file except in compliance with
  the License.  You may obtain a copy of the License at

      http://www.apache.org/licenses/LICENSE-2.0

  Unless required by applicable law or agreed to in writing, software
  distributed under the License is distributed on an "AS IS" BASIS,
  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  See the License for the specific language governing permissions and
  limitations under the License.
--&gt;
&lt;!-- Note:  A "Server" is not itself a "Container", so you may not
     define subcomponents such as "Valves" at this level.
     Documentation at /docs/config/server.html
 --&gt;
&lt;Server port="8005" shutdown="SHUTDOWN"&gt;

  &lt;!--APR library loader. Documentation at /docs/apr.html --&gt;
  &lt;Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" /&gt;
  &lt;!--Initialize Jasper prior to webapps are loaded. Documentation at /docs/jasper-howto.html --&gt;
  &lt;Listener className="org.apache.catalina.core.JasperListener" /&gt;
  &lt;!-- JMX Support for the Tomcat server. Documentation at /docs/non-existent.html --&gt;
  &lt;Listener className="org.apache.catalina.mbeans.ServerLifecycleListener" /&gt;
  &lt;Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" /&gt;

  &lt;!-- Global JNDI resources
       Documentation at /docs/jndi-resources-howto.html
  --&gt;
  &lt;GlobalNamingResources&gt;
    &lt;!-- Editable user database that can also be used by
         UserDatabaseRealm to authenticate users
    --&gt;
    &lt;Resource name="UserDatabase" auth="Container"
              type="org.apache.catalina.UserDatabase"
              description="User database that can be updated and saved"
              factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
              pathname="conf/tomcat-users.xml" /&gt;
  &lt;/GlobalNamingResources&gt;

  &lt;!-- A "Service" is a collection of one or more "Connectors" that share
       a single "Container" Note:  A "Service" is not itself a "Container",
       so you may not define subcomponents such as "Valves" at this level.
       Documentation at /docs/config/service.html
   --&gt;
  &lt;Service name="Catalina"&gt;

    &lt;!--The connectors can use a shared executor, you can define one or more named thread pools--&gt;
    &lt;!--
    &lt;Executor name="tomcatThreadPool" namePrefix="catalina-exec-"
        maxThreads="150" minSpareThreads="4"/&gt;
    --&gt;


    &lt;!-- A "Connector" represents an endpoint by which requests are received
         and responses are returned. Documentation at :
         Java HTTP Connector: /docs/config/http.html (blocking &amp; non-blocking)
         Java AJP  Connector: /docs/config/ajp.html
         APR (HTTP/AJP) Connector: /docs/apr.html
         Define a non-SSL HTTP/1.1 Connector on port 8080
    --&gt;
  &lt;!-- &lt;Connector port="8080" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443" /&gt;  --&gt;
    &lt;!-- A "Connector" using the shared thread pool--&gt;
    &lt;!--
    &lt;Connector executor="tomcatThreadPool"
               port="8080" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443" /&gt;
    --&gt;
    &lt;!-- Define a SSL HTTP/1.1 Connector on port 8443
         This connector uses the JSSE configuration, when using APR, the
         connector should be using the OpenSSL style configuration
         described in the APR documentation --&gt;

    &lt;Connector  port="8443"
                protocol="org.apache.coyote.http11.Http11Protocol"
                ciphers="SSL_RSA_WITH_RC4_128_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA"
                SSLEnabled="true"
                enableLookups="false"
                disableUploadTimeout="true"
                acceptCount="100"
                maxThreads="200"
                scheme="https"
                secure="true"
                clientAuth="false"
                keystoreFile="/home/touchnet/ssl/keystore.wc"
                keystorePass="&lt;removedforwiki&gt;"
                sslProtocol="TLS"
      /&gt;

    &lt;!-- Define an AJP 1.3 Connector on port 8009 --&gt;
    &lt;Connector port="8009" protocol="AJP/1.3" redirectPort="8443" /&gt;


    &lt;!-- An Engine represents the entry point (within Catalina) that processes
         every request.  The Engine implementation for Tomcat stand alone
         analyzes the HTTP headers included with the request, and passes them
         on to the appropriate Host (virtual host).
         Documentation at /docs/config/engine.html --&gt;

    &lt;!-- You should set jvmRoute to support load-balancing via AJP ie :
    &lt;Engine name="Catalina" defaultHost="localhost" jvmRoute="jvm1"&gt;
    --&gt;
    &lt;Engine name="Catalina" defaultHost="localhost"&gt;

      &lt;!--For clustering, please take a look at documentation at:
          /docs/cluster-howto.html  (simple how to)
          /docs/config/cluster.html (reference documentation) --&gt;
      &lt;!--
      &lt;Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster"/&gt;
      --&gt;

      &lt;!-- The request dumper valve dumps useful debugging information about
           the request and response data received and sent by Tomcat.
           Documentation at: /docs/config/valve.html --&gt;
      &lt;!--
      &lt;Valve className="org.apache.catalina.valves.RequestDumperValve"/&gt;
      --&gt;

      &lt;!-- This Realm uses the UserDatabase configured in the global JNDI
           resources under the key "UserDatabase".  Any edits
           that are performed against this UserDatabase are immediately
           available for use by the Realm.  --&gt;
      &lt;Realm className="org.apache.catalina.realm.UserDatabaseRealm"
             resourceName="UserDatabase" digest="SHA" /&gt;

      &lt;!-- Define the default virtual host
           Note: XML Schema validation will not work with Xerces 2.2.
       --&gt;
      &lt;Host name="localhost"  appBase="webapps"
            unpackWARs="true" autoDeploy="true"
            xmlValidation="false" xmlNamespaceAware="false"&gt;

        &lt;!-- SingleSignOn valve, share authentication between web applications
             Documentation at: /docs/config/valve.html --&gt;
        &lt;!--
        &lt;Valve className="org.apache.catalina.authenticator.SingleSignOn" /&gt;
        --&gt;

        &lt;!-- Access log processes all example.
             Documentation at: /docs/config/valve.html --&gt;
        &lt;!--
        &lt;Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"
               prefix="localhost_access_log." suffix=".txt" pattern="common" resolveHosts="false"/&gt;
        --&gt;

      &lt;/Host&gt;
    &lt;/Engine&gt;
  &lt;/Service&gt;
&lt;/Server&gt;
{code}</property>
    

<property name="body">h2. First Step


h5. If IP is assigned by DHCP, make sure /etc/hosts file looks like this:
{code:title=/etc/hosts|borderStyle=solid}127.0.0.1     servername.suu.edu     localhost.localdomain     localhost     servername
{code}

h5. If IP is hard-coded, make sure /etc/hosts file looks like this (x.x is your new IP):
{code:title=/etc/hosts|borderStyle=solid}127.0.0.1     localhost.localdomain     localhost
134.250.x.x   yourserver.suu.edu        yourserver
{code}

h2. Second Step


h5. If you need the change to happen immediately without a reboot, run the following command as root:
{code:borderStyle=solid}#hostname yourserver.suu.edu
{code}

h2. Third Step


h5. This step is optional, and depends on the linux distribution and version you are using.  If you have an /etc/HOSTNAME file, ensure that it is populated with a single line as follows:
{code:borderStyle=solid}yourserver.suu.edu
{code}

h2. Fourth Step


h5. Edit the /etc/sysconfig/network file HOSTNAME line to read:
{code:title=/etc/sysconfig/network|borderStyle=solid}HOSTNAME=yourserver.suu.edu
{code}

h2. Fifth Step


h5. As root, run the following command:
{code:borderStyle=solid}#echo yourserver.suu.edu &gt; /proc/sys/kernel/hostname

To verify that it worked, run:
#cat /proc/sys/kernel/hostname
{code}

h2. Sixth Step


h5. Edit the /etc/sysconfig/network-scripts/ifcfg-eth0 file
{code}
DEVICE=eth0
BOOTPROTO=static (or dhcp)
ONBOOT=yes
HWADDR=[MAC Address]
NETMASK=255.255.255.0
IPADDR=[YOURIP]
GATEWAY=[YOURGW]
Type=Ethernet
{code}
h2. Finally, reboot.</property>
    

<property name="body">h4. /&lt;tomcat_home&gt;/conf/Catalina/localhost/manager.xml
{code}
&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0?

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
--&gt;
&lt;!--

Context configuration file for the Tomcat Manager Web App

$Id: manager.xml 562814 2007-08-05 03:52:04Z markt $

--&gt;

&lt;Context docBase="${catalina.home}/webapps/manager" privileged="true" antiResourceLocking="false" antiJARLocking="false"&gt;
&lt;Valve className="org.apache.catalina.valves.RemoteAddrValve" allow="127.0.0.1,134.250.4.*"/&gt;
&lt;/Context&gt;
{code}

h4. /&lt;tomcat_home&gt;/conf/server.xml
{code}
&lt;?xml version='1.0' encoding='utf-8'?&gt;
&lt;!--
  Licensed to the Apache Software Foundation (ASF) under one or more
  contributor license agreements.  See the NOTICE file distributed with
  this work for additional information regarding copyright ownership.
  The ASF licenses this file to You under the Apache License, Version 2.0
  (the "License"); you may not use this file except in compliance with
  the License.  You may obtain a copy of the License at

      http://www.apache.org/licenses/LICENSE-2.0

  Unless required by applicable law or agreed to in writing, software
  distributed under the License is distributed on an "AS IS" BASIS,
  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  See the License for the specific language governing permissions and
  limitations under the License.
--&gt;
&lt;!-- Note:  A "Server" is not itself a "Container", so you may not
     define subcomponents such as "Valves" at this level.
     Documentation at /docs/config/server.html
 --&gt;
&lt;Server port="8005" shutdown="SHUTDOWN"&gt;

  &lt;!--APR library loader. Documentation at /docs/apr.html --&gt;
  &lt;Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" /&gt;
  &lt;!--Initialize Jasper prior to webapps are loaded. Documentation at /docs/jasper-howto.html --&gt;
  &lt;Listener className="org.apache.catalina.core.JasperListener" /&gt;
  &lt;!-- JMX Support for the Tomcat server. Documentation at /docs/non-existent.html --&gt;
  &lt;Listener className="org.apache.catalina.mbeans.ServerLifecycleListener" /&gt;
  &lt;Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" /&gt;

  &lt;!-- Global JNDI resources
       Documentation at /docs/jndi-resources-howto.html
  --&gt;
  &lt;GlobalNamingResources&gt;
    &lt;!-- Editable user database that can also be used by
         UserDatabaseRealm to authenticate users
    --&gt;
    &lt;Resource name="UserDatabase" auth="Container"
              type="org.apache.catalina.UserDatabase"
              description="User database that can be updated and saved"
              factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
              pathname="conf/tomcat-users.xml" /&gt;
  &lt;/GlobalNamingResources&gt;

  &lt;!-- A "Service" is a collection of one or more "Connectors" that share
       a single "Container" Note:  A "Service" is not itself a "Container",
       so you may not define subcomponents such as "Valves" at this level.
       Documentation at /docs/config/service.html
   --&gt;
  &lt;Service name="Catalina"&gt;

    &lt;!--The connectors can use a shared executor, you can define one or more named thread pools--&gt;
    &lt;!--
    &lt;Executor name="tomcatThreadPool" namePrefix="catalina-exec-"
        maxThreads="150" minSpareThreads="4"/&gt;
    --&gt;


    &lt;!-- A "Connector" represents an endpoint by which requests are received
         and responses are returned. Documentation at :
         Java HTTP Connector: /docs/config/http.html (blocking &amp; non-blocking)
         Java AJP  Connector: /docs/config/ajp.html
         APR (HTTP/AJP) Connector: /docs/apr.html
         Define a non-SSL HTTP/1.1 Connector on port 8080
    --&gt;
  &lt;!-- &lt;Connector port="8080" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443" /&gt;  --&gt;
    &lt;!-- A "Connector" using the shared thread pool--&gt;
    &lt;!--
    &lt;Connector executor="tomcatThreadPool"
               port="8080" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443" /&gt;
    --&gt;
    &lt;!-- Define a SSL HTTP/1.1 Connector on port 8443
         This connector uses the JSSE configuration, when using APR, the
         connector should be using the OpenSSL style configuration
         described in the APR documentation --&gt;

    &lt;Connector  port="8443"
                protocol="org.apache.coyote.http11.Http11Protocol"
                ciphers="SSL_RSA_WITH_RC4_128_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA"
                SSLEnabled="true"
                enableLookups="false"
                disableUploadTimeout="true"
                acceptCount="100"
                maxThreads="200"
                scheme="https"
                secure="true"
                clientAuth="false"
                keystoreFile="/home/touchnet/ssl/keystore.wc"
                keystorePass="&lt;removedforwiki&gt;"
                sslProtocol="TLS"
      /&gt;

    &lt;!-- Define an AJP 1.3 Connector on port 8009 --&gt;
    &lt;Connector port="8009" protocol="AJP/1.3" redirectPort="8443" /&gt;


    &lt;!-- An Engine represents the entry point (within Catalina) that processes
         every request.  The Engine implementation for Tomcat stand alone
         analyzes the HTTP headers included with the request, and passes them
         on to the appropriate Host (virtual host).
         Documentation at /docs/config/engine.html --&gt;

    &lt;!-- You should set jvmRoute to support load-balancing via AJP ie :
    &lt;Engine name="Catalina" defaultHost="localhost" jvmRoute="jvm1"&gt;
    --&gt;
    &lt;Engine name="Catalina" defaultHost="localhost"&gt;

      &lt;!--For clustering, please take a look at documentation at:
          /docs/cluster-howto.html  (simple how to)
          /docs/config/cluster.html (reference documentation) --&gt;
      &lt;!--
      &lt;Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster"/&gt;
      --&gt;

      &lt;!-- The request dumper valve dumps useful debugging information about
           the request and response data received and sent by Tomcat.
           Documentation at: /docs/config/valve.html --&gt;
      &lt;!--
      &lt;Valve className="org.apache.catalina.valves.RequestDumperValve"/&gt;
      --&gt;

      &lt;!-- This Realm uses the UserDatabase configured in the global JNDI
           resources under the key "UserDatabase".  Any edits
           that are performed against this UserDatabase are immediately
           available for use by the Realm.  --&gt;
      &lt;Realm className="org.apache.catalina.realm.UserDatabaseRealm"
             resourceName="UserDatabase" digest="SHA" /&gt;

      &lt;!-- Define the default virtual host
           Note: XML Schema validation will not work with Xerces 2.2.
       --&gt;
      &lt;Host name="localhost"  appBase="webapps"
            unpackWARs="true" autoDeploy="true"
            xmlValidation="false" xmlNamespaceAware="false"&gt;

        &lt;!-- SingleSignOn valve, share authentication between web applications
             Documentation at: /docs/config/valve.html --&gt;
        &lt;!--
        &lt;Valve className="org.apache.catalina.authenticator.SingleSignOn" /&gt;
        --&gt;

        &lt;!-- Access log processes all example.
             Documentation at: /docs/config/valve.html --&gt;
        &lt;!--
        &lt;Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"
               prefix="localhost_access_log." suffix=".txt" pattern="common" resolveHosts="false"/&gt;
        --&gt;

      &lt;/Host&gt;
    &lt;/Engine&gt;
  &lt;/Service&gt;
&lt;/Server&gt;
{code}</property>
    

<property name="body">h4. /&lt;tomcat_home&gt;/conf/Catalina/localhost/manager.xml
{code}
&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0?

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
--&gt;
&lt;!--

Context configuration file for the Tomcat Manager Web App

$Id: manager.xml 562814 2007-08-05 03:52:04Z markt $

--&gt;

&lt;Context docBase="${catalina.home}/webapps/manager" privileged="true" antiResourceLocking="false" antiJARLocking="false"&gt;
&lt;Valve className="org.apache.catalina.valves.RemoteAddrValve" allow="127.0.0.1,134.250.4.*"/&gt;
&lt;/Context&gt;
{code}

h4. /&lt;tomcat_home&gt;/conf/server.xml
{code}
&lt;?xml version='1.0' encoding='utf-8'?&gt;
&lt;!--
  Licensed to the Apache Software Foundation (ASF) under one or more
  contributor license agreements.  See the NOTICE file distributed with
  this work for additional information regarding copyright ownership.
  The ASF licenses this file to You under the Apache License, Version 2.0
  (the "License"); you may not use this file except in compliance with
  the License.  You may obtain a copy of the License at

      http://www.apache.org/licenses/LICENSE-2.0

  Unless required by applicable law or agreed to in writing, software
  distributed under the License is distributed on an "AS IS" BASIS,
  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  See the License for the specific language governing permissions and
  limitations under the License.
--&gt;
&lt;!-- Note:  A "Server" is not itself a "Container", so you may not
     define subcomponents such as "Valves" at this level.
     Documentation at /docs/config/server.html
 --&gt;
&lt;Server port="8005" shutdown="SHUTDOWN"&gt;

  &lt;!--APR library loader. Documentation at /docs/apr.html --&gt;
  &lt;Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" /&gt;
  &lt;!--Initialize Jasper prior to webapps are loaded. Documentation at /docs/jasper-howto.html --&gt;
  &lt;Listener className="org.apache.catalina.core.JasperListener" /&gt;
  &lt;!-- JMX Support for the Tomcat server. Documentation at /docs/non-existent.html --&gt;
  &lt;Listener className="org.apache.catalina.mbeans.ServerLifecycleListener" /&gt;
  &lt;Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" /&gt;

  &lt;!-- Global JNDI resources
       Documentation at /docs/jndi-resources-howto.html
  --&gt;
  &lt;GlobalNamingResources&gt;
    &lt;!-- Editable user database that can also be used by
         UserDatabaseRealm to authenticate users
    --&gt;
    &lt;Resource name="UserDatabase" auth="Container"
              type="org.apache.catalina.UserDatabase"
              description="User database that can be updated and saved"
              factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
              pathname="conf/tomcat-users.xml" /&gt;
  &lt;/GlobalNamingResources&gt;

  &lt;!-- A "Service" is a collection of one or more "Connectors" that share
       a single "Container" Note:  A "Service" is not itself a "Container",
       so you may not define subcomponents such as "Valves" at this level.
       Documentation at /docs/config/service.html
   --&gt;
  &lt;Service name="Catalina"&gt;

    &lt;!--The connectors can use a shared executor, you can define one or more named thread pools--&gt;
    &lt;!--
    &lt;Executor name="tomcatThreadPool" namePrefix="catalina-exec-"
        maxThreads="150" minSpareThreads="4"/&gt;
    --&gt;


    &lt;!-- A "Connector" represents an endpoint by which requests are received
         and responses are returned. Documentation at :
         Java HTTP Connector: /docs/config/http.html (blocking &amp; non-blocking)
         Java AJP  Connector: /docs/config/ajp.html
         APR (HTTP/AJP) Connector: /docs/apr.html
         Define a non-SSL HTTP/1.1 Connector on port 8080
    --&gt;
  &lt;!-- &lt;Connector port="8080" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443" /&gt;  --&gt;
    &lt;!-- A "Connector" using the shared thread pool--&gt;
    &lt;!--
    &lt;Connector executor="tomcatThreadPool"
               port="8080" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443" /&gt;
    --&gt;
    &lt;!-- Define a SSL HTTP/1.1 Connector on port 8443
         This connector uses the JSSE configuration, when using APR, the
         connector should be using the OpenSSL style configuration
         described in the APR documentation --&gt;

    &lt;Connector  port="8443"
                protocol="org.apache.coyote.http11.Http11Protocol"
                ciphers="SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA"
              SSLEnabled="true"
                enableLookups="false"
                disableUploadTimeout="true"
                acceptCount="100"
                maxThreads="200"
                scheme="https"
                secure="true"
                clientAuth="false"
                keystoreFile="/home/touchnet/ssl/keystore.wc"
                keystorePass="&lt;removedforwiki&gt;"
                sslProtocol="TLS"
      /&gt;

    &lt;!-- Define an AJP 1.3 Connector on port 8009 --&gt;
    &lt;Connector port="8009" protocol="AJP/1.3" redirectPort="8443" /&gt;


    &lt;!-- An Engine represents the entry point (within Catalina) that processes
         every request.  The Engine implementation for Tomcat stand alone
         analyzes the HTTP headers included with the request, and passes them
         on to the appropriate Host (virtual host).
         Documentation at /docs/config/engine.html --&gt;

    &lt;!-- You should set jvmRoute to support load-balancing via AJP ie :
    &lt;Engine name="Catalina" defaultHost="localhost" jvmRoute="jvm1"&gt;
    --&gt;
    &lt;Engine name="Catalina" defaultHost="localhost"&gt;

      &lt;!--For clustering, please take a look at documentation at:
          /docs/cluster-howto.html  (simple how to)
          /docs/config/cluster.html (reference documentation) --&gt;
      &lt;!--
      &lt;Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster"/&gt;
      --&gt;

      &lt;!-- The request dumper valve dumps useful debugging information about
           the request and response data received and sent by Tomcat.
           Documentation at: /docs/config/valve.html --&gt;
      &lt;!--
      &lt;Valve className="org.apache.catalina.valves.RequestDumperValve"/&gt;
      --&gt;

      &lt;!-- This Realm uses the UserDatabase configured in the global JNDI
           resources under the key "UserDatabase".  Any edits
           that are performed against this UserDatabase are immediately
           available for use by the Realm.  --&gt;
      &lt;Realm className="org.apache.catalina.realm.UserDatabaseRealm"
             resourceName="UserDatabase" digest="SHA" /&gt;

      &lt;!-- Define the default virtual host
           Note: XML Schema validation will not work with Xerces 2.2.
       --&gt;
      &lt;Host name="localhost"  appBase="webapps"
            unpackWARs="true" autoDeploy="true"
            xmlValidation="false" xmlNamespaceAware="false"&gt;

        &lt;!-- SingleSignOn valve, share authentication between web applications
             Documentation at: /docs/config/valve.html --&gt;
        &lt;!--
        &lt;Valve className="org.apache.catalina.authenticator.SingleSignOn" /&gt;
        --&gt;

        &lt;!-- Access log processes all example.
             Documentation at: /docs/config/valve.html --&gt;
        &lt;!--
        &lt;Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"
               prefix="localhost_access_log." suffix=".txt" pattern="common" resolveHosts="false"/&gt;
        --&gt;

      &lt;/Host&gt;
    &lt;/Engine&gt;
  &lt;/Service&gt;
&lt;/Server&gt;
{code}</property>
    

<property name="body">&lt;h4&gt;Current /etc/apt/mirror.list contents&lt;/h4&gt;
&lt;ac:structured-macro ac:macro-id="e502af34-96f4-4882-870c-b5b17ea9f48a" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
############# config ##################
#
set base_path    /home/itftp/APTMIRROR
#
# if you change the base path you must create the directories below with write privileges
#
set mirror_path  $base_path/mirror
set skel_path    $base_path/skel
set var_path     $base_path/var
set cleanscript  $base_path/var/clean.sh
set defaultarch  i386
set nthreads     10
set _tilde 0
#
############# end config ##############
# Main packages for hardy, jaunty, lucid, maverick
deb-i386 http://archive.ubuntu.com/ubuntu hardy main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu hardy-updates main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu hardy main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu hardy-updates main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu jaunty main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu jaunty-updates main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu jaunty main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu jaunty-updates main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu lucid main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu lucid-updates main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu lucid main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu lucid-updates main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu maverick main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu maverick-updates main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu maverick main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu maverick-updates main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu natty main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu natty-updates main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu natty main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu natty-updates main restricted universe multiverse

# Updates for hardy, jaunty, lucid, maverick
deb-i386 http://archive.ubuntu.com/ubuntu hardy-security main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu hardy-security main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu jaunty-security main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu jaunty-security main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu lucid-security main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu lucid-security main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu maverick-security main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu maverick-security main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu natty-security main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu natty-security main restricted universe multiverse
# Security updates
deb-i386 http://security.ubuntu.com/ubuntu hardy-security main restricted
deb-i386 http://security.ubuntu.com/ubuntu hardy-security universe
deb-i386 http://security.ubuntu.com/ubuntu hardy-security multiverse
deb-amd64 http://security.ubuntu.com/ubuntu hardy-security main restricted
deb-amd64 http://security.ubuntu.com/ubuntu hardy-security universe
deb-amd64 http://security.ubuntu.com/ubuntu hardy-security multiverse
deb-i386 http://security.ubuntu.com/ubuntu jaunty-security main restricted
deb-i386 http://security.ubuntu.com/ubuntu jaunty-security universe
deb-i386 http://security.ubuntu.com/ubuntu jaunty-security multiverse
deb-amd64 http://security.ubuntu.com/ubuntu jaunty-security main restricted
deb-amd64 http://security.ubuntu.com/ubuntu jaunty-security universe
deb-amd64 http://security.ubuntu.com/ubuntu jaunty-security multiverse
deb-i386 http://security.ubuntu.com/ubuntu lucid-security main restricted
deb-i386 http://security.ubuntu.com/ubuntu lucid-security universe
deb-i386 http://security.ubuntu.com/ubuntu lucid-security multiverse
deb-amd64 http://security.ubuntu.com/ubuntu lucid-security main restricted
deb-amd64 http://security.ubuntu.com/ubuntu lucid-security universe
deb-amd64 http://security.ubuntu.com/ubuntu lucid-security multiverse
deb-i386 http://security.ubuntu.com/ubuntu maverick-security main restricted
deb-i386 http://security.ubuntu.com/ubuntu maverick-security universe
deb-i386 http://security.ubuntu.com/ubuntu maverick-security multiverse
deb-amd64 http://security.ubuntu.com/ubuntu maverick-security main restricted
deb-amd64 http://security.ubuntu.com/ubuntu maverick-security universe
deb-amd64 http://security.ubuntu.com/ubuntu maverick-security multiverse
deb-i386 http://security.ubuntu.com/ubuntu natty-security main restricted
deb-i386 http://security.ubuntu.com/ubuntu natty-security universe
deb-i386 http://security.ubuntu.com/ubuntu natty-security multiverse
deb-amd64 http://security.ubuntu.com/ubuntu natty-security main restricted
deb-amd64 http://security.ubuntu.com/ubuntu natty-security universe
deb-amd64 http://security.ubuntu.com/ubuntu natty-security multiverse
# Partner repo
deb-i386 http://archive.canonical.com/ubuntu hardy partner
deb-amd64 http://archive.canonical.com/ubuntu hardy partner
deb-i386 http://archive.canonical.com/ubuntu jaunty partner
deb-amd64 http://archive.canonical.com/ubuntu jaunty partner
deb-i386 http://archive.canonical.com/ubuntu lucid partner
deb-amd64 http://archive.canonical.com/ubuntu lucid partner
deb-i386 http://archive.canonical.com/ubuntu maverick partner
deb-amd64 http://archive.canonical.com/ubuntu maverick partner
deb-i386 http://archive.canonical.com/ubuntu natty partner
deb-amd64 http://archive.canonical.com/ubuntu natty partner

# Extras (added as of Maverick)
deb-i386 http://extras.ubuntu.com/ubuntu maverick main
deb-amd64 http://extras.ubuntu.com/ubuntu maverick main
deb-i386 http://extras.ubuntu.com/ubuntu natty main
deb-amd64 http://extras.ubuntu.com/ubuntu natty main

# Cleanup scripts
clean http://archive.ubuntu.com
clean http://security.ubuntu.com
clean http://archive.canonical.com
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;
&lt;h4&gt;Current soft links in /var/www directory&lt;/h4&gt;
&lt;ac:structured-macro ac:macro-id="59053279-499e-484c-9d57-91cc1f88b91b" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
root@sherpa:/var/www# ls -aslh
total 12K
4.0K drwxr-xr-x  2 root root 4.0K 2011-06-03 16:44 .
4.0K drwxr-xr-x 15 root root 4.0K 2011-06-02 16:58 ..
   0 lrwxrwxrwx  1 root root   53 2011-06-03 16:44 extras -&gt; /home/itftp/APTMIRROR/mirror/extras.ubuntu.com/ubuntu
4.0K -rw-r--r--  1 root root  177 2011-06-02 16:58 index.html
   0 lrwxrwxrwx  1 root root   54 2011-06-03 09:46 ubuntu -&gt; /home/itftp/APTMIRROR/mirror/archive.ubuntu.com/ubuntu
   0 lrwxrwxrwx  1 root root   57 2011-06-03 09:46 ubuntupartner -&gt; /home/itftp/APTMIRROR/mirror/archive.canonical.com/ubuntu
   0 lrwxrwxrwx  1 root root   55 2011-06-03 09:46 updates -&gt; /home/itftp/APTMIRROR/mirror/security.ubuntu.com/ubuntu
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;</property>
    

<property name="body">h4. Current /etc/apt/mirror.list contents
{code}
############# config ##################
#
set base_path    /home/itftp/APTMIRROR
#
# if you change the base path you must create the directories below with write privileges
#
set mirror_path  $base_path/mirror
set skel_path    $base_path/skel
set var_path     $base_path/var
set cleanscript  $base_path/var/clean.sh
set defaultarch  i386
set nthreads     10
set _tilde 0
#
############# end config ##############
# Main packages for hardy, jaunty, lucid, maverick
deb-i386 http://archive.ubuntu.com/ubuntu hardy main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu hardy-updates main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu hardy main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu hardy-updates main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu jaunty main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu jaunty-updates main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu jaunty main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu jaunty-updates main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu lucid main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu lucid-updates main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu lucid main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu lucid-updates main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu maverick main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu maverick-updates main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu maverick main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu maverick-updates main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu natty main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu natty-updates main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu natty main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu natty-updates main restricted universe multiverse

# Updates for hardy, jaunty, lucid, maverick
deb-i386 http://archive.ubuntu.com/ubuntu hardy-security main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu hardy-security main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu jaunty-security main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu jaunty-security main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu lucid-security main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu lucid-security main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu maverick-security main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu maverick-security main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu natty-security main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu natty-security main restricted universe multiverse
# Security updates
deb-i386 http://security.ubuntu.com/ubuntu hardy-security main restricted
deb-i386 http://security.ubuntu.com/ubuntu hardy-security universe
deb-i386 http://security.ubuntu.com/ubuntu hardy-security multiverse
deb-amd64 http://security.ubuntu.com/ubuntu hardy-security main restricted
deb-amd64 http://security.ubuntu.com/ubuntu hardy-security universe
deb-amd64 http://security.ubuntu.com/ubuntu hardy-security multiverse
deb-i386 http://security.ubuntu.com/ubuntu jaunty-security main restricted
deb-i386 http://security.ubuntu.com/ubuntu jaunty-security universe
deb-i386 http://security.ubuntu.com/ubuntu jaunty-security multiverse
deb-amd64 http://security.ubuntu.com/ubuntu jaunty-security main restricted
deb-amd64 http://security.ubuntu.com/ubuntu jaunty-security universe
deb-amd64 http://security.ubuntu.com/ubuntu jaunty-security multiverse
deb-i386 http://security.ubuntu.com/ubuntu lucid-security main restricted
deb-i386 http://security.ubuntu.com/ubuntu lucid-security universe
deb-i386 http://security.ubuntu.com/ubuntu lucid-security multiverse
deb-amd64 http://security.ubuntu.com/ubuntu lucid-security main restricted
deb-amd64 http://security.ubuntu.com/ubuntu lucid-security universe
deb-amd64 http://security.ubuntu.com/ubuntu lucid-security multiverse
deb-i386 http://security.ubuntu.com/ubuntu maverick-security main restricted
deb-i386 http://security.ubuntu.com/ubuntu maverick-security universe
deb-i386 http://security.ubuntu.com/ubuntu maverick-security multiverse
deb-amd64 http://security.ubuntu.com/ubuntu maverick-security main restricted
deb-amd64 http://security.ubuntu.com/ubuntu maverick-security universe
deb-amd64 http://security.ubuntu.com/ubuntu maverick-security multiverse
deb-i386 http://security.ubuntu.com/ubuntu natty-security main restricted
deb-i386 http://security.ubuntu.com/ubuntu natty-security universe
deb-i386 http://security.ubuntu.com/ubuntu natty-security multiverse
deb-amd64 http://security.ubuntu.com/ubuntu natty-security main restricted
deb-amd64 http://security.ubuntu.com/ubuntu natty-security universe
deb-amd64 http://security.ubuntu.com/ubuntu natty-security multiverse
# Partner repo
deb-i386 http://archive.canonical.com/ubuntu hardy partner
deb-amd64 http://archive.canonical.com/ubuntu hardy partner
deb-i386 http://archive.canonical.com/ubuntu jaunty partner
deb-amd64 http://archive.canonical.com/ubuntu jaunty partner
deb-i386 http://archive.canonical.com/ubuntu lucid partner
deb-amd64 http://archive.canonical.com/ubuntu lucid partner
deb-i386 http://archive.canonical.com/ubuntu maverick partner
deb-amd64 http://archive.canonical.com/ubuntu maverick partner
deb-i386 http://archive.canonical.com/ubuntu natty partner
deb-amd64 http://archive.canonical.com/ubuntu natty partner

# Extras (added as of Maverick)
deb-i386 http://extras.ubuntu.com/ubuntu maverick main
deb-amd64 http://extras.ubuntu.com/ubuntu maverick main
deb-i386 http://extras.ubuntu.com/ubuntu natty main
deb-amd64 http://extras.ubuntu.com/ubuntu natty main

# Cleanup scripts
clean http://archive.ubuntu.com
clean http://security.ubuntu.com
clean http://archive.canonical.com
{code}
</property>
    

<property name="body">&lt;ac:macro ac:name="suu-info"&gt;&lt;ac:rich-text-body&gt;
&lt;p&gt;This is the root page for our HAProxy documentation.&lt;/p&gt;&lt;/ac:rich-text-body&gt;&lt;/ac:macro&gt;

&lt;ac:macro ac:name="suu-tip"&gt;&lt;ac:rich-text-body&gt;
&lt;p&gt;&lt;strong&gt;How to check on the status of things&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;&lt;strong&gt;Check status of HAProxy&lt;/strong&gt;
	&lt;ul&gt;
		&lt;li&gt;&lt;a class="external-link" href="http://halb1.suu.edu:8001" rel="nofollow"&gt;http://halb1.suu.edu:8001&lt;/a&gt;&lt;/li&gt;
		&lt;li&gt;&lt;a class="external-link" href="http://halb2.suu.edu:8001" rel="nofollow"&gt;http://halb2.suu.edu:8001&lt;/a&gt;&lt;/li&gt;
		&lt;li&gt;&lt;a class="external-link" href="http://halb3.suu.edu:8001" rel="nofollow"&gt;http://halb3.suu.edu:8001&lt;/a&gt;&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
	&lt;li&gt;&lt;strong&gt;Check the status of the nodes&lt;/strong&gt;
	&lt;ul&gt;
		&lt;li&gt;SSH into one of the nodes
&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="24c2d397-302e-4385-aaf0-001958d51f54"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
ssh halb1.suu.edu
sudo crm_mon --one-shot -V | grep Online
# The output will look something like this:
Online: [ halb1 halb2 halb3 ]
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;/li&gt;
	&lt;/ul&gt;
	&lt;/li&gt;
&lt;/ul&gt;

&lt;/ac:rich-text-body&gt;&lt;/ac:macro&gt;


&lt;h2&gt;Overview&lt;/h2&gt;

&lt;ul&gt;
	&lt;li&gt;We have three load balancer nodes running in a cluster. They are active/active and will automatically take over for the other if one goes down.&lt;/li&gt;
	&lt;li&gt;The load balance cluster has multiple shared IP addresses. The shared IP addresses are the user-facing IPs and that is where firewall rules are applied for user access.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Current production setup example: (note we have more stuff behind our load balancers, but this demonstrates the basic idea.)&lt;/p&gt;
&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="3e2c4a7c-6d41-49f2-94e0-bf409b8679e7"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[

        shared IP=12.141
            ^^^^^^^^
       12.142      12.143       5.24  5.25  
 -------+------------+-----------+-----+---
        |            |           |     |   
     +--+--+      +--+--+      +-+-+ +-+-+ 
     | LB1 |      | LB2 |      | A | | B | 
     +-----+      +-----+      +---+ +---+ 
     haproxy      haproxy       web servers
     heartbeat    heartbeat
     pacemaker    pacemaker

]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;
&lt;p&gt;&lt;strong&gt;LB1&lt;/strong&gt; = halb1.suu.edu&lt;br /&gt;
&lt;strong&gt;LB2&lt;/strong&gt; = halb2.suu.edu&lt;br /&gt;
&lt;strong&gt;A&lt;/strong&gt; = api1.suu.edu&lt;br /&gt;
&lt;strong&gt;B&lt;/strong&gt; = api2.suu.edu&lt;br /&gt;
&lt;strong&gt;shared IP&lt;/strong&gt; = api.suu.edu&lt;/p&gt;</property>
    

<property name="body">h2. Install Apache

{code}
sudo apt-get install apache2 libapache2-mod-proxy-html
a2enmod ssl
a2enmod proxy
{code}

h2. Apache SSL

Get our wildcard certificate and private key.

{code}
sudo mv server.crt /etc/ssl/certs/suu_edu.crt
sudo mv server.key /etc/ssl/private/suu_edu.key
{code}

h2. Configure Apache Virtual Host

{code}
cd /etc/apache2/sites-available/
sudo cp default-ssl api-ssl
sudo vim api-ssl
# 
{code}</property>
    

<property name="body">h2. Install Apache

{code}
sudo apt-get install apache2 libapache2-mod-proxy-html
a2enmod ssl
a2enmod proxy
{code}

h2. Apache SSL

Get our wildcard certificate and private key.

{code}
sudo mv server.crt /etc/ssl/certs/suu_edu.crt
sudo mv server.key /etc/ssl/private/suu_edu.key
{code}

h2. Configure Apache Virtual Host

{code}
cd /etc/apache2/sites-available/
sudo cp default-ssl api-ssl
sudo vim api-ssl
# 
{code}

h2. Install HAProxy

{code}
sudo apt-get install haproxy
{code}</property>
    

<property name="body">h2. Install Apache

{code}
sudo apt-get install apache2 libapache2-mod-proxy-html
a2enmod ssl
a2enmod proxy
{code}

h2. Apache SSL

Get our wildcard certificate and private key.

{code}
sudo mv server.crt /etc/ssl/certs/suu_edu.crt
sudo mv server.key /etc/ssl/private/suu_edu.key
{code}

h2. Configure Apache Virtual Host

{code}
cd /etc/apache2/sites-available/
sudo cp default-ssl api-ssl
sudo vim api-ssl
# 
{code}

h2. Install HAProxy

# http://www.howtoforge.com/setting-up-a-high-availability-load-balancer-with-haproxy-wackamole-spread-on-debian-etch
# 

{code}
sudo apt-get install haproxy
{code}</property>
    

<property name="body">h2. Install Apache

{code}
sudo apt-get install apache2 libapache2-mod-proxy-html
a2enmod ssl
a2enmod proxy
{code}

h2. Apache SSL

Get our wildcard certificate and private key.

{code}
sudo mv server.crt /etc/ssl/certs/suu_edu.crt
sudo mv server.key /etc/ssl/private/suu_edu.key
{code}

h2. Configure Apache Virtual Host

{code}
cd /etc/apache2/sites-available/
sudo cp default-ssl api-ssl
sudo vim api-ssl
# 
{code}

h2. Install HAProxy

# http://www.zivtech.com/blog/setting-ip-failover-heartbeat-and-pacemaker-ubuntu-lucid

{code}
sudo apt-get install haproxy
{code}

h2. Install heartbeat and pacemaker

{code}
sudo apt-get install heartbeat pacemaker
{code}

*Create ha.cf file (main heartbeat config file)*
{code}
sudo vim /etc/ha.d/ha.cf
# Add the following
autojoin none
bcast eth0
warntime 5
deadtime 15
initdead 60
keepalive 2
node halb1
node halb2
crm respawn
{code}

*Create authkeys file for heartbeat*
The following run as a shell script will generate the key, create the authkeys file and set proper permissions on the file.
{code}
#!/bin/bash
( echo -ne "auth 1\n1 sha1 "; \
  dd if=/dev/urandom bs=512 count=1 | openssl md5 ) \
  &gt; /etc/ha.d/authkeys
chmod 0600 /etc/ha.d/authkeys
{code}

*Restart heartbeat*
{code}
sudo /etc/init.d/heartbeat restart
{code}

*Verify that they are online*
{code}
sudo crm_mon -1 | grep Online
{code}

*Configure shared IPAddress*
This is part of Pacemaker. To Pacemaker, an ipaddress is a resource.

{suu-note}
The following commands only need to be run on one node. They will be replicated automatically to the second node.
*api_ip* - is just the name we came up with to name this ip resource. This one is for the ip that will be used for api.suu.edu
*eth0" - the nic we want this ip to use.
{suu-note}

{code}
sudo crm configure property stonith-enabled=false
sudo crm configure
crm(live)configure# primitive api_ip IPaddr params ip=134.250.12.141 cidr_netmask="255.255.255.0" nic="eth0"
crm(live)configure# commit
crm(live)configure# exit
{code}

*Set a preferred node for the ip resource*
This tells Pacemaker which node the resource ip should live on when both nodes are up.
{code}
sudo crm configure
crm(live)configure# location api_ip_pref api_ip 100: halb1
crm(live)configure# commit
crm(live)configure# exit
{code}

*Setup Pacemaker monitoring*
{code}
sudo crm configure
crm(live)configure# monitor api_ip 15s:5s
crm(live)configure# commit
crm(live)configure# exit
{code}

*Show running configuration*
{code}
sudo crm configure show
{code}

</property>
    

<property name="body">&lt;ac:macro ac:name="suu-info"&gt;&lt;ac:rich-text-body&gt;
&lt;p&gt;These are the steps you need to take to put a new service behind our HAProxy load balancers.&lt;br /&gt;
This document assumes that you already have your services running that you want to balance and that both load balancer nodes have appropriate firewall rules in place to access those services.&lt;/p&gt;&lt;/ac:rich-text-body&gt;&lt;/ac:macro&gt;

&lt;h2&gt;Setup HAProxy&lt;/h2&gt;
&lt;ac:macro ac:name="suu-info"&gt;&lt;ac:rich-text-body&gt;
&lt;ul&gt;
	&lt;li&gt;You will need to modify the same file on both load balancer nodes.&lt;/li&gt;
	&lt;li&gt;Both load balancer nodes need to have the appropriate firewall rules in place to get to your servers before this point.&lt;/li&gt;
	&lt;li&gt;You should also know the front-facing ipaddress that your service will be using for this step.&lt;/li&gt;
&lt;/ul&gt;
&lt;/ac:rich-text-body&gt;&lt;/ac:macro&gt;
&lt;p&gt;&lt;strong&gt;Edit &lt;code&gt;/etc/haproxy/haproxy.cfg&lt;/code&gt; (on both nodes)&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;You will be adding a new server farm. Here is an example farm.&lt;/p&gt;

&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="d24b2078-0ce9-46cd-a3c4-f878a39b657f"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
listen  api-webfarm 134.250.12.142:8000
        mode http
        balance roundrobin
        option httpclose
        option forwardfor
        option httpchk GET /banner
        server api1 134.250.5.24:8080 maxconn 1 check
        server api2 134.250.5.25:8080 maxconn 1 check
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;
&lt;p&gt;&lt;ac:emoticon ac:name="warning" /&gt; The listen port must be unique, so if 8000 and 8001 are taken, use 8002&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Restart haproxy&lt;/strong&gt;&lt;/p&gt;
&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="42e769d3-5039-445e-b6fc-c23d6ca3ddf9"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
sudo /etc/init.d/haproxy restart
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;

&lt;p&gt;&lt;strong&gt;Commit your changes&lt;/strong&gt;&lt;/p&gt;
&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="7099d610-457f-4edf-9391-09fad55f090a"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
cd /etc/haproxy/
sudo hg commit -m "New server config."
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;

&lt;ac:macro ac:name="suu-tip"&gt;&lt;ac:rich-text-body&gt;
&lt;p&gt;At this point, you should be able to see if HAProxy thinks your service is up or down by going to:
&lt;a class="external-link" href="http://halb1.suu.edu:8001" rel="nofollow"&gt;http://halb1.suu.edu:8001&lt;/a&gt;
&lt;a class="external-link" href="http://halb2.suu.edu:8001" rel="nofollow"&gt;http://halb2.suu.edu:8001&lt;/a&gt;&lt;/p&gt;&lt;/ac:rich-text-body&gt;&lt;/ac:macro&gt;

&lt;h2&gt;Setup Apache&lt;/h2&gt;
&lt;ac:macro ac:name="suu-info"&gt;&lt;ac:rich-text-body&gt;
&lt;ul&gt;
	&lt;li&gt;The same configuration will go on both load balander nodes, however, they are not exactly the same. IP addresses will be different.&lt;/li&gt;
	&lt;li&gt;You can probably use an existing apache virtual host config file as a starting point. All you really need to do is then change ipaddresses and ports. No need to change the ssl settings because we are using our wildcard certificate.&lt;/li&gt;
&lt;/ul&gt;
&lt;/ac:rich-text-body&gt;&lt;/ac:macro&gt;

&lt;ol&gt;
	&lt;li&gt;Create a new virtual host configuration
&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="8f668288-381b-4403-bd3a-f755d7a87a16"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
sudo cp /etc/apache2/sites-available/api-ssl /etc/apache2/sites-available/yourservice-ssl
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;/li&gt;
	&lt;li&gt;Modify yourservice-ssl
&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="962c290b-203c-4bfb-aaff-7e8ee178c485"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
sudo vim /etc/apache2/sites-available/yourservice-ssl
# Edit the ipaddress ie &lt;VirtualHost 134.250.12.141:443&gt; This should be the front-facing ipaddress for your application. The one that users will be connecting to.
# Edit just the ports in ProxyPass and ProxyPassReverse. The ports would be the haproxy ports you configured in the HAProxy step above.
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;/li&gt;
	&lt;li&gt;Enable your new virtual host
&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="1d88ee80-7ff1-46ea-9d08-12e658373850"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
sudo a2ensite yourservice-ssl
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;/li&gt;
	&lt;li&gt;Reload apache
&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="dec61e9f-b213-4a57-9c3b-e003e051f5ae"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
sudo /etc/init.d/apache2 reload
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;/li&gt;
	&lt;li&gt;Commit your changes
&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="0adbb605-fc2c-4dc8-a2ea-c316fc965543"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
cd /etc/apache2/sites-available/
sudo hg add yourservice-ssl
sudo hg commit -m "New virtual host config file."
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;/li&gt;
	&lt;li&gt;Now do the same thing on the other load balancer node, but make sure the IP addresses for the &lt;strong&gt;&lt;code&gt;ProxyPass&lt;/code&gt;&lt;/strong&gt; and &lt;strong&gt;&lt;code&gt;ProxyPassReverse&lt;/code&gt;&lt;/strong&gt; are set to the IP address of that node.&lt;/li&gt;
&lt;/ol&gt;


&lt;h2&gt;Setup your front-facing ipaddress&lt;/h2&gt;
&lt;ac:macro ac:name="suu-info"&gt;&lt;ac:rich-text-body&gt;
&lt;ul&gt;
	&lt;li&gt;This step only needs to be done on one of the load balancer nodes. It will be automatically replicated to the second node.&lt;/li&gt;
	&lt;li&gt;What you are doing here is setting up the ipaddress that users will hit. It is a shared ipaddress between the two nodes. This configuration is handled by Pacemaker&lt;/li&gt;
&lt;/ul&gt;
&lt;/ac:rich-text-body&gt;&lt;/ac:macro&gt;

&lt;ac:macro ac:name="suu-tip"&gt;&lt;ac:rich-text-body&gt;
&lt;p&gt;&lt;strong&gt;Tip:&lt;/strong&gt;&lt;br /&gt;
The following commands only need to be run on one node. They will be replicated automatically to the second node.&lt;br /&gt;
&lt;strong&gt;api_ip&lt;/strong&gt; - is just the name we came up with to name this ip resource. This one is for the ip that will be used for api.suu.edu&lt;br /&gt;
*eth0&amp;quot; - the nic we want this ip to use.&lt;/p&gt;&lt;/ac:rich-text-body&gt;&lt;/ac:macro&gt;

&lt;ol&gt;
	&lt;li&gt;&lt;strong&gt;Setup ipaddress resource&lt;/strong&gt;
&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="3af3710a-ac6f-4907-b0ef-2d3c2a8c3577"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
sudo crm configure
crm(live)configure# primitive api_ip IPaddr params ip=134.250.12.141 cidr_netmask=255.255.255.0 nic=eth0
crm(live)configure# commit
crm(live)configure# exit
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;/li&gt;
	&lt;li&gt;&lt;strong&gt;Set a preferred node for the ip resource&lt;/strong&gt;&lt;br /&gt;
This tells Pacemaker which node the resource ip should live on when both nodes are up.
&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="988fc79e-d299-4d23-ace2-db9daddba225"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
sudo crm configure
crm(live)configure# location api_ip_pref api_ip 100: halb1
crm(live)configure# commit
crm(live)configure# exit
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;/li&gt;
	&lt;li&gt;&lt;strong&gt;Setup Pacemaker monitoring&lt;/strong&gt;
&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="b47bc63b-9f6a-45ac-bbc3-2234906bdab4"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
sudo crm configure
crm(live)configure# monitor api_ip 40s:20s
crm(live)configure# commit
crm(live)configure# exit
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;/li&gt;
	&lt;li&gt;&lt;strong&gt;Show running configuration&lt;/strong&gt;
&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="a863556d-82f2-4700-b308-bcdfba7ee339"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
sudo crm configure show
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;/li&gt;
&lt;/ol&gt;


&lt;ac:macro ac:name="suu-tip"&gt;&lt;ac:rich-text-body&gt;
&lt;p&gt;At this point, you should be able to hit your service on your front-facing ipaddress port 443 and get a response from your service.&lt;/p&gt;&lt;/ac:rich-text-body&gt;&lt;/ac:macro&gt;</property>
    

<property name="body">{suu-info}
These are the steps you need to take to put a new service behind our HAProxy load balancers.
This document assumes that you already have your services running that you want to balance and that both load balancer nodes have appropriate firewall rules in place to access those services.
{suu-info}

h2. Setup HAProxy

* You will need to modify the same file on both load balancer nodes.
* Both load balancer nodes need to have the appropriate firewall rules in place to get to your servers before this point.
* You should also know the front-facing ipaddress that your service will be using for this step.

*Edit {{/etc/haproxy/haproxy.cfg}} (on both nodes)*

You will be adding a new server farm. Here is an example farm.

{code}
listen  api-webfarm 134.250.12.142:8000
        mode http
        balance roundrobin
        option httpclose
        option forwardfor
        option httpchk GET /banner
        server api1 134.250.5.24:8080 maxconn 1 check
        server api2 134.250.5.24:8080 maxconn 1 check
{code}
(!) The listen port must be unique, so if 8000 and 8001 are taken, use 8002

*Restart haproxy*
{code}
sudo /etc/init.d/haproxy restart
{code}

{suu-tip}
At this point, you should be able to see if HAProxy thinks your service is up or down by going to:
http://halb1.suu.edu:8001
http://halb2.suu.edu:8001
{suu-tip}

h2. Setup Apache

* You will need to do the same configuration on both load balancer nodes.
* You can probably use an existing apache virtual host config file as a starting point. All you really need to do is then change ipaddresses and ports. No need to change the ssl settings because we are using our wildcard certificate.

# Create a new virtual host configuration
{code}
sudo cp /etc/apache2/sites-available/api-ssl /etc/apache2/sites-available/yourservice-ssl
{code}
# Modify yourservice-ssl
{code}
sudo vim /etc/apache2/sites-available/yourservice-ssl
# Edit the ipaddress ie &lt;VirtualHost 134.250.12.141:443&gt; This should be the front-facing ipaddress for your application. The one that users will be connecting to.
# Edit just the ports in ProxyPass and ProxyPassReverse. The ports would be the haproxy ports you configured in the HAProxy step above.
{code}
# Enable your new virtual host
{code}
sudo a2ensite yourservice-ssl
{code}
# Reload apache
{code}
sudo /etc/init.d/apache2 reload
{code}

h2. Setup your front-facing ipaddress

* This step only needs to be done on one of the load balancer nodes. It will be automatically replicated to the second node.
* What you are doing here is setting up the ipaddress that users will hit. It is a shared ipaddress between the two nodes. This configuration is handled by Pacemaker



</property>
    

<property name="body">{suu-info}
These are the steps you need to take to put a new service behind our HAProxy load balancers.
This document assumes that you already have your services running that you want to balance and that both load balancer nodes have appropriate firewall rules in place to access those services.
{suu-info}

h2. Setup HAProxy

* You will need to modify the same file on both load balancer nodes.
* Both load balancer nodes need to have the appropriate firewall rules in place to get to your servers before this point.
* You should also know the front-facing ipaddress that your service will be using for this step.

*Edit {{/etc/haproxy/haproxy.cfg}} (on both nodes)*

You will be adding a new server farm. Here is an example farm.

{code}
listen  api-webfarm 134.250.12.142:8000
        mode http
        balance roundrobin
        option httpclose
        option forwardfor
        option httpchk GET /banner
        server api1 134.250.5.24:8080 maxconn 1 check
        server api2 134.250.5.24:8080 maxconn 1 check
{code}
(!) The listen port must be unique, so if 8000 and 8001 are taken, use 8002

*Restart haproxy*
{code}
sudo /etc/init.d/haproxy restart
{code}

{suu-tip}
At this point, you should be able to see if HAProxy thinks your service is up or down by going to:
http://halb1.suu.edu:8001
http://halb2.suu.edu:8001
{suu-tip}

h2. Setup Apache

* You will need to do the same configuration on both load balancer nodes.
* You can probably use an existing apache virtual host config file as a starting point. All you really need to do is then change ipaddresses and ports. No need to change the ssl settings because we are using our wildcard certificate.

# Create a new virtual host configuration
{code}
sudo cp /etc/apache2/sites-available/api-ssl /etc/apache2/sites-available/yourservice-ssl
{code}
# Modify yourservice-ssl
{code}
sudo vim /etc/apache2/sites-available/yourservice-ssl
# Edit the ipaddress ie &lt;VirtualHost 134.250.12.141:443&gt; This should be the front-facing ipaddress for your application. The one that users will be connecting to.
# Edit just the ports in ProxyPass and ProxyPassReverse. The ports would be the haproxy ports you configured in the HAProxy step above.
{code}
# Enable your new virtual host
{code}
sudo a2ensite yourservice-ssl
{code}
# Reload apache
{code}
sudo /etc/init.d/apache2 reload
{code}

h2. Setup your front-facing ipaddress

* This step only needs to be done on one of the load balancer nodes. It will be automatically replicated to the second node.
* What you are doing here is setting up the ipaddress that users will hit. It is a shared ipaddress between the two nodes. This configuration is handled by Pacemaker

{suu-tip}
*Tip:*
The following commands only need to be run on one node. They will be replicated automatically to the second node.
*api_ip* - is just the name we came up with to name this ip resource. This one is for the ip that will be used for api.suu.edu
*eth0" - the nic we want this ip to use.
{suu-tip}

# *Setup ipaddress resource*
{code}
sudo crm configure property stonith-enabled=false
sudo crm configure
crm(live)configure# primitive api_ip IPaddr params ip=134.250.12.141 cidr_netmask="255.255.255.0" nic="eth0"
crm(live)configure# commit
crm(live)configure# exit
{code}
# *Set a preferred node for the ip resource*
This tells Pacemaker which node the resource ip should live on when both nodes are up.
{code}
sudo crm configure
crm(live)configure# location api_ip_pref api_ip 100: halb1
crm(live)configure# commit
crm(live)configure# exit
{code}
# *Setup Pacemaker monitoring*
{code}
sudo crm configure
crm(live)configure# monitor api_ip 15s:5s
crm(live)configure# commit
crm(live)configure# exit
{code}
# *Show running configuration*
{code}
sudo crm configure show
{code}

{suu-tip}
At this point, you should be able to hit your service on your front-facing ipaddress port 443 and get a response from your service.
{suu-tip}</property>
    

<property name="body">{suu-info}
These are the steps you need to take to put a new service behind our HAProxy load balancers.
This document assumes that you already have your services running that you want to balance and that both load balancer nodes have appropriate firewall rules in place to access those services.
{suu-info}

h2. Setup HAProxy

* You will need to modify the same file on both load balancer nodes.
* Both load balancer nodes need to have the appropriate firewall rules in place to get to your servers before this point.
* You should also know the front-facing ipaddress that your service will be using for this step.

*Edit {{/etc/haproxy/haproxy.cfg}} (on both nodes)*

You will be adding a new server farm. Here is an example farm.

{code}
listen  api-webfarm 134.250.12.142:8000
        mode http
        balance roundrobin
        option httpclose
        option forwardfor
        option httpchk GET /banner
        server api1 134.250.5.24:8080 maxconn 1 check
        server api2 134.250.5.24:8080 maxconn 1 check
{code}
(!) The listen port must be unique, so if 8000 and 8001 are taken, use 8002

*Restart haproxy*
{code}
sudo /etc/init.d/haproxy restart
{code}

{suu-tip}
At this point, you should be able to see if HAProxy thinks your service is up or down by going to:
http://halb1.suu.edu:8001
http://halb2.suu.edu:8001
{suu-tip}

h2. Setup Apache

* You will need to do the same configuration on both load balancer nodes.
* You can probably use an existing apache virtual host config file as a starting point. All you really need to do is then change ipaddresses and ports. No need to change the ssl settings because we are using our wildcard certificate.

# Create a new virtual host configuration
{code}
sudo cp /etc/apache2/sites-available/api-ssl /etc/apache2/sites-available/yourservice-ssl
{code}
# Modify yourservice-ssl
{code}
sudo vim /etc/apache2/sites-available/yourservice-ssl
# Edit the ipaddress ie &lt;VirtualHost 134.250.12.141:443&gt; This should be the front-facing ipaddress for your application. The one that users will be connecting to.
# Edit just the ports in ProxyPass and ProxyPassReverse. The ports would be the haproxy ports you configured in the HAProxy step above.
{code}
# Enable your new virtual host
{code}
sudo a2ensite yourservice-ssl
{code}
# Reload apache
{code}
sudo /etc/init.d/apache2 reload
{code}

h2. Setup your front-facing ipaddress

* This step only needs to be done on one of the load balancer nodes. It will be automatically replicated to the second node.
* What you are doing here is setting up the ipaddress that users will hit. It is a shared ipaddress between the two nodes. This configuration is handled by Pacemaker

{suu-tip}
*Tip:*
The following commands only need to be run on one node. They will be replicated automatically to the second node.
*api_ip* - is just the name we came up with to name this ip resource. This one is for the ip that will be used for api.suu.edu
*eth0" - the nic we want this ip to use.
{suu-tip}

# *Setup ipaddress resource*
{code}
sudo crm configure
crm(live)configure# primitive api_ip IPaddr params ip=134.250.12.141 cidr_netmask="255.255.255.0" nic="eth0"
crm(live)configure# commit
crm(live)configure# exit
{code}
# *Set a preferred node for the ip resource*
This tells Pacemaker which node the resource ip should live on when both nodes are up.
{code}
sudo crm configure
crm(live)configure# location api_ip_pref api_ip 100: halb1
crm(live)configure# commit
crm(live)configure# exit
{code}
# *Setup Pacemaker monitoring*
{code}
sudo crm configure
crm(live)configure# monitor api_ip 15s:5s
crm(live)configure# commit
crm(live)configure# exit
{code}
# *Show running configuration*
{code}
sudo crm configure show
{code}

{suu-tip}
At this point, you should be able to hit your service on your front-facing ipaddress port 443 and get a response from your service.
{suu-tip}</property>
    

<property name="body">&lt;h2&gt;Install Apache&lt;/h2&gt;&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="37d8a760-3789-4805-90ad-ac9fbee775ef"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[ 
sudo apt-get install apache2 libapache2-mod-proxy-html 
a2enmod ssl 
a2enmod proxy
a2enmod proxy_http
sudo service apache2 restart
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;h2&gt;Configure Apache to run on ports 445, 5001, and 5000 in addition to the defaults&lt;/h2&gt;&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="51ec960a-53b6-49ab-8b0c-add78b2d7c45"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[# Edit apache ports file to listen on additional ports
vim /etc/apache/ports.conf
# It should look like the following:
 
 
# If you just change the port or add more ports here, you will likely also
# have to change the VirtualHost statement in
# /etc/apache2/sites-enabled/000-default
# This is also true if you have upgraded from before 2.2.9-3 (i.e. from
# Debian etch). See /usr/share/doc/apache2.2-common/NEWS.Debian.gz and
# README.Debian.gz
#NameVirtualHost *:80
Listen 80
Listen 81
&lt;IfModule mod_ssl.c&gt;
    # If you add NameVirtualHost *:443 here, you will also have to change
    # the VirtualHost statement in /etc/apache2/sites-available/default-ssl
    # to &lt;VirtualHost *:443&gt;
    # Server Name Indication for SSL named virtual hosts is currently not
    # supported by MSIE on Windows XP.
Listen 443
Listen 445
Listen 5001
Listen 5000
&lt;/IfModule&gt;
&lt;IfModule mod_gnutls.c&gt;
Listen 443
Listen 445
Listen 5001
Listen 5000
&lt;/IfModule&gt;]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;h2&gt;Apache SSL&lt;/h2&gt;&lt;p&gt;Get our wildcard certificate and private key.&lt;/p&gt;&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="22c8f4e8-6fd0-4fb2-8156-f785e11604b4"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[ 
sudo mv server.crt /etc/ssl/certs/suu_edu.crt 
sudo mv server.key /etc/ssl/private/suu_edu.key 

sudo mv RapidSSL_CA_Bundle.pem /etc/ssl/certs/]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;h2&gt;Configure Apache Virtual Host&lt;/h2&gt;&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="4b051ac2-1171-4e9e-8f75-61e030dd30fc"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[ 
Copy all files from working node (e.g. halb1) /etc/apache2/sites-available/ 
Remove default-ssl
Ensure default has correct site restrictions for server-status

]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;h2&gt;Install HAProxy&lt;/h2&gt;&lt;ol&gt;&lt;li&gt;&lt;a class="external-link" href="http://www.zivtech.com/blog/setting-ip-failover-heartbeat-and-pacemaker-ubuntu-lucid" rel="nofollow"&gt;http://www.zivtech.com/blog/setting-ip-failover-heartbeat-and-pacemaker-ubuntu-lucid&lt;/a&gt;&lt;/li&gt;&lt;/ol&gt;&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="d7cc412b-1132-46e1-9312-ec1680ed7d23"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[ 
sudo apt-get install haproxy 
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;h2&gt;Install heartbeat and pacemaker&lt;/h2&gt;&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="d326df89-da94-43d2-a806-3cd3babefb07"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[ 
sudo apt-get install heartbeat pacemaker 
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;p&gt;&lt;strong&gt;Create ha.cf file (main heartbeat config file)&lt;/strong&gt;&lt;/p&gt;&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="3eaed0e4-715f-4789-af7e-c6a86487e4e3"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[Copy working ha.cf file from another node (e.g. halb1), being sure to add your new node to the list.  It should look something like this 
sudo vim /etc/ha.d/ha.cf 
autojoin any
bcast eth0
warntime 5
deadtime 15
initdead 60
keepalive 2
node halb1
node halb2
node halb3
node halb4
crm respawn


]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;h2&gt;Modify /etc/default/haproxy file&lt;/h2&gt;&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="3ad77fdb-6c36-4bd4-87c7-fc2acbd89953"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[ENABLED=1
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;p&gt;&lt;strong&gt;Create authkeys file for heartbeat&lt;/strong&gt; (original node only)&lt;br /&gt; The following run as a shell script will generate the key, create the authkeys file and set proper permissions on the file.&lt;/p&gt;&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="9ada7795-e7f4-4075-b8b7-4699cc611ed0"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[ 
#!/bin/bash 
( echo -ne "auth 1\n1 sha1 "; dd if=/dev/urandom bs=512 count=1 | openssl md5 ) &gt; /etc/ha.d/authkeys
exit 

 
#chmod 0600 /etc/ha.d/authkeys 
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;p&gt;If this is an addtional node, simply copy the authkeys from the original server to your new node&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Copy existing haproxy.cfg&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="435b39b6-ac58-441d-9105-cef6730dcad3"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[Copy an existing /etc/haproxy/haproxy.cfg file from a working node to your new node.]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Restart heartbeat&lt;/strong&gt;&lt;/p&gt;&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="d060755b-3ee3-4b06-9687-f06abcbdb12a"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[ 
sudo /etc/init.d/heartbeat restart 
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;p&gt;&lt;strong&gt;&lt;strong&gt;Restart haproxy&lt;/strong&gt;&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="cda45460-06ca-4701-852c-a5d324560804"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[sudo /etc/init.d/haproxy restart ]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Verify that they are online&lt;/strong&gt;&lt;/p&gt;&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="ac43636c-2703-4a1f-9ce2-dd3e661bc3f2"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[ 
sudo crm_mon -1 | grep Online 
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;p&gt;&lt;strong&gt;Configure shared IPAddress&lt;/strong&gt; &lt;br /&gt; This is part of Pacemaker. To Pacemaker, an ipaddress is a resource.&lt;/p&gt;&lt;ac:macro ac:name="suu-tip"&gt;&lt;ac:parameter ac:name="atlassian-macro-output-type"&gt;BLOCK&lt;/ac:parameter&gt;&lt;ac:rich-text-body&gt;&lt;p&gt;&lt;strong&gt;Tip:&lt;/strong&gt; &lt;br /&gt; The following commands only need to be run on one node. They will be replicated automatically to the second node. &lt;br /&gt; &lt;strong&gt;api_ip&lt;/strong&gt; - is just the name we came up with to name this ip resource. This one is for the ip that will be used for api.suu.edu &lt;br /&gt; *eth0&amp;quot; - the nic we want this ip to use.&lt;/p&gt;&lt;/ac:rich-text-body&gt;&lt;/ac:macro&gt;&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="43aea737-3b8e-4beb-ade0-1dd0f5676823"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[ 
sudo crm configure property stonith-enabled=false 
sudo crm configure 
crm(live)configure# primitive api_ip IPaddr params ip=134.250.12.141 cidr_netmask="255.255.255.0" nic="eth0" 
crm(live)configure# commit 
crm(live)configure# exit 
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;p&gt;&lt;strong&gt;Set a preferred node for the ip resource&lt;/strong&gt; &lt;br /&gt; This tells Pacemaker which node the resource ip should live on when both nodes are up.&lt;/p&gt;&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="42f49261-82ef-45a2-b1ed-42da3809ec57"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[ 
sudo crm configure 
crm(live)configure# location api_ip_pref api_ip 100: halb1 
crm(live)configure# commit 
crm(live)configure# exit 
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;p&gt;&lt;strong&gt;Setup Pacemaker monitoring&lt;/strong&gt;&lt;/p&gt;&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="cabfc831-cb5d-4b47-ae71-9434b3ecd8b5"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[ 
sudo crm configure 
crm(live)configure# monitor api_ip 15s:5s 
crm(live)configure# commit 
crm(live)configure# exit 
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;p&gt;&lt;strong&gt;Show running configuration&lt;/strong&gt;&lt;/p&gt;&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="7a7b1ab2-d13b-4f97-a500-6b385a660272"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[ 
sudo crm configure show 
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;p&gt;&lt;strong&gt;Allow IP Addresses to bind even if they are not assigned to a particular node&lt;/strong&gt;&lt;/p&gt;&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="716c695f-8560-43e2-bc32-2ede2c1af63d"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[sudo vim /etc/sysctl.conf
# Add the following line to the bottom of the file
net.ipv4.ip_nonlocal_bind=1
# Save, and reboot]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;</property>
    

<property name="body">h2. Install Apache

{code}
sudo apt-get install apache2 libapache2-mod-proxy-html
a2enmod ssl
a2enmod proxy
{code}

h2. Apache SSL

Get our wildcard certificate and private key.

{code}
sudo mv server.crt /etc/ssl/certs/suu_edu.crt
sudo mv server.key /etc/ssl/private/suu_edu.key
{code}

h2. Configure Apache Virtual Host

{code}
cd /etc/apache2/sites-available/
sudo cp default-ssl api-ssl
sudo vim api-ssl
# 
{code}

h2. Install HAProxy

# http://www.zivtech.com/blog/setting-ip-failover-heartbeat-and-pacemaker-ubuntu-lucid

{code}
sudo apt-get install haproxy
{code}

h2. Install heartbeat and pacemaker

{code}
sudo apt-get install heartbeat pacemaker
{code}

*Create ha.cf file (main heartbeat config file)*
{code}
sudo vim /etc/ha.d/ha.cf
# Add the following
autojoin none
bcast eth0
warntime 5
deadtime 15
initdead 60
keepalive 2
node halb1
node halb2
crm respawn
{code}

*Create authkeys file for heartbeat*
The following run as a shell script will generate the key, create the authkeys file and set proper permissions on the file.
{code}
#!/bin/bash
( echo -ne "auth 1\n1 sha1 "; \
  dd if=/dev/urandom bs=512 count=1 | openssl md5 ) \
  &gt; /etc/ha.d/authkeys
chmod 0600 /etc/ha.d/authkeys
{code}

*Restart heartbeat*
{code}
sudo /etc/init.d/heartbeat restart
{code}

*Verify that they are online*
{code}
sudo crm_mon -1 | grep Online
{code}

*Configure shared IPAddress*
This is part of Pacemaker. To Pacemaker, an ipaddress is a resource.

{suu-tip}
*Tip:*
The following commands only need to be run on one node. They will be replicated automatically to the second node.
*api_ip* - is just the name we came up with to name this ip resource. This one is for the ip that will be used for api.suu.edu
*eth0" - the nic we want this ip to use.
{suu-tip}

{code}
sudo crm configure property stonith-enabled=false
sudo crm configure
crm(live)configure# primitive api_ip IPaddr params ip=134.250.12.141 cidr_netmask="255.255.255.0" nic="eth0"
crm(live)configure# commit
crm(live)configure# exit
{code}

*Set a preferred node for the ip resource*
This tells Pacemaker which node the resource ip should live on when both nodes are up.
{code}
sudo crm configure
crm(live)configure# location api_ip_pref api_ip 100: halb1
crm(live)configure# commit
crm(live)configure# exit
{code}

*Setup Pacemaker monitoring*
{code}
sudo crm configure
crm(live)configure# monitor api_ip 15s:5s
crm(live)configure# commit
crm(live)configure# exit
{code}

*Show running configuration*
{code}
sudo crm configure show
{code}

</property>
    

<property name="body">{suu-info}
These are the steps you need to take to put a new service behind our HAProxy load balancers.
This document assumes that you already have your services running that you want to balance and that both load balancer nodes have appropriate firewall rules in place to access those services.
{suu-info}

h2. Setup HAProxy
{suu-info}
* You will need to modify the same file on both load balancer nodes.
* Both load balancer nodes need to have the appropriate firewall rules in place to get to your servers before this point.
* You should also know the front-facing ipaddress that your service will be using for this step.
{suu-info}
*Edit {{/etc/haproxy/haproxy.cfg}} (on both nodes)*

You will be adding a new server farm. Here is an example farm.

{code}
listen  api-webfarm 134.250.12.142:8000
        mode http
        balance roundrobin
        option httpclose
        option forwardfor
        option httpchk GET /banner
        server api1 134.250.5.24:8080 maxconn 1 check
        server api2 134.250.5.24:8080 maxconn 1 check
{code}
(!) The listen port must be unique, so if 8000 and 8001 are taken, use 8002

*Restart haproxy*
{code}
sudo /etc/init.d/haproxy restart
{code}

{suu-tip}
At this point, you should be able to see if HAProxy thinks your service is up or down by going to:
http://halb1.suu.edu:8001
http://halb2.suu.edu:8001
{suu-tip}

h2. Setup Apache
{suu-info}
* The same configuration will go on both load balander nodes. We will make the changes on one server and replicate them to the other server using Mercurial.
* You can probably use an existing apache virtual host config file as a starting point. All you really need to do is then change ipaddresses and ports. No need to change the ssl settings because we are using our wildcard certificate.
{suu-info}

# Create a new virtual host configuration
{code}
sudo cp /etc/apache2/sites-available/api-ssl /etc/apache2/sites-available/yourservice-ssl
{code}
# Modify yourservice-ssl
{code}
sudo vim /etc/apache2/sites-available/yourservice-ssl
# Edit the ipaddress ie &lt;VirtualHost 134.250.12.141:443&gt; This should be the front-facing ipaddress for your application. The one that users will be connecting to.
# Edit just the ports in ProxyPass and ProxyPassReverse. The ports would be the haproxy ports you configured in the HAProxy step above.
{code}
# Enable your new virtual host
{code}
sudo a2ensite yourservice-ssl
{code}
# Reload apache
{code}
sudo /etc/init.d/apache2 reload
{code}
# Now we need to get the same config on the other load balancer node:
{code}
# First commit the virtual host file on the first node
cd /etc/apache2/sites-available
sudo hg add yourservice-ssl
sudo hg commit -m "New virtual host config file."
sudo hg push
# Now we can go grab that on the other server
ssh halb2.suu.edu
cd /etc/apache2/sites-available
sudo hg pull
sudo hg update
sudo a2ensite yourservice-ssl
sudo /etc/init.d/apache2 reload
{code}

h2. Setup your front-facing ipaddress
{suu-info}
* This step only needs to be done on one of the load balancer nodes. It will be automatically replicated to the second node.
* What you are doing here is setting up the ipaddress that users will hit. It is a shared ipaddress between the two nodes. This configuration is handled by Pacemaker
{suu-info}

{suu-tip}
*Tip:*
The following commands only need to be run on one node. They will be replicated automatically to the second node.
*api_ip* - is just the name we came up with to name this ip resource. This one is for the ip that will be used for api.suu.edu
*eth0" - the nic we want this ip to use.
{suu-tip}

# *Setup ipaddress resource*
{code}
sudo crm configure
crm(live)configure# primitive api_ip IPaddr params ip=134.250.12.141 cidr_netmask="255.255.255.0" nic="eth0"
crm(live)configure# commit
crm(live)configure# exit
{code}
# *Set a preferred node for the ip resource*
This tells Pacemaker which node the resource ip should live on when both nodes are up.
{code}
sudo crm configure
crm(live)configure# location api_ip_pref api_ip 100: halb1
crm(live)configure# commit
crm(live)configure# exit
{code}
# *Setup Pacemaker monitoring*
{code}
sudo crm configure
crm(live)configure# monitor api_ip 40s:20s
crm(live)configure# commit
crm(live)configure# exit
{code}
# *Show running configuration*
{code}
sudo crm configure show
{code}

{suu-tip}
At this point, you should be able to hit your service on your front-facing ipaddress port 443 and get a response from your service.
{suu-tip}</property>
    

<property name="body">{suu-info}
These are the steps you need to take to put a new service behind our HAProxy load balancers.
This document assumes that you already have your services running that you want to balance and that both load balancer nodes have appropriate firewall rules in place to access those services.
{suu-info}

h2. Setup HAProxy
{suu-info}
* You will need to modify the same file on both load balancer nodes.
* Both load balancer nodes need to have the appropriate firewall rules in place to get to your servers before this point.
* You should also know the front-facing ipaddress that your service will be using for this step.
{suu-info}
*Edit {{/etc/haproxy/haproxy.cfg}} (on both nodes)*

You will be adding a new server farm. Here is an example farm.

{code}
listen  api-webfarm 134.250.12.142:8000
        mode http
        balance roundrobin
        option httpclose
        option forwardfor
        option httpchk GET /banner
        server api1 134.250.5.24:8080 maxconn 1 check
        server api2 134.250.5.24:8080 maxconn 1 check
{code}
(!) The listen port must be unique, so if 8000 and 8001 are taken, use 8002

*Restart haproxy*
{code}
sudo /etc/init.d/haproxy restart
{code}

*Commit your changes*
{code}
cd /etc/haproxy/
sudo hg commit -m "New server config."
{code}

{suu-tip}
At this point, you should be able to see if HAProxy thinks your service is up or down by going to:
http://halb1.suu.edu:8001
http://halb2.suu.edu:8001
{suu-tip}

h2. Setup Apache
{suu-info}
* The same configuration will go on both load balander nodes, however, they are not exactly the same. IP addresses will be different.
* You can probably use an existing apache virtual host config file as a starting point. All you really need to do is then change ipaddresses and ports. No need to change the ssl settings because we are using our wildcard certificate.
{suu-info}

# Create a new virtual host configuration
{code}
sudo cp /etc/apache2/sites-available/api-ssl /etc/apache2/sites-available/yourservice-ssl
{code}
# Modify yourservice-ssl
{code}
sudo vim /etc/apache2/sites-available/yourservice-ssl
# Edit the ipaddress ie &lt;VirtualHost 134.250.12.141:443&gt; This should be the front-facing ipaddress for your application. The one that users will be connecting to.
# Edit just the ports in ProxyPass and ProxyPassReverse. The ports would be the haproxy ports you configured in the HAProxy step above.
{code}
# Enable your new virtual host
{code}
sudo a2ensite yourservice-ssl
{code}
# Reload apache
{code}
sudo /etc/init.d/apache2 reload
{code}
# Commit your changes
{code}
cd /etc/apache2/sites-available/
sudo hg add yourservice-ssl
sudo hg commit -m "New virtual host config file."
{code}
# Now do the same thing on the other load balancer node, but make sure the IP addresses for the *{{ProxyPass}}* and *{{ProxyPassReverse}}* are set to the IP address of that node.

h2. Setup your front-facing ipaddress
{suu-info}
* This step only needs to be done on one of the load balancer nodes. It will be automatically replicated to the second node.
* What you are doing here is setting up the ipaddress that users will hit. It is a shared ipaddress between the two nodes. This configuration is handled by Pacemaker
{suu-info}

{suu-tip}
*Tip:*
The following commands only need to be run on one node. They will be replicated automatically to the second node.
*api_ip* - is just the name we came up with to name this ip resource. This one is for the ip that will be used for api.suu.edu
*eth0" - the nic we want this ip to use.
{suu-tip}

# *Setup ipaddress resource*
{code}
sudo crm configure
crm(live)configure# primitive api_ip IPaddr params ip=134.250.12.141 cidr_netmask="255.255.255.0" nic="eth0"
crm(live)configure# commit
crm(live)configure# exit
{code}
# *Set a preferred node for the ip resource*
This tells Pacemaker which node the resource ip should live on when both nodes are up.
{code}
sudo crm configure
crm(live)configure# location api_ip_pref api_ip 100: halb1
crm(live)configure# commit
crm(live)configure# exit
{code}
# *Setup Pacemaker monitoring*
{code}
sudo crm configure
crm(live)configure# monitor api_ip 40s:20s
crm(live)configure# commit
crm(live)configure# exit
{code}
# *Show running configuration*
{code}
sudo crm configure show
{code}

{suu-tip}
At this point, you should be able to hit your service on your front-facing ipaddress port 443 and get a response from your service.
{suu-tip}</property>
    

<property name="body">{suu-info}
These are the steps you need to take to put a new service behind our HAProxy load balancers.
This document assumes that you already have your services running that you want to balance and that both load balancer nodes have appropriate firewall rules in place to access those services.
{suu-info}

h2. Setup HAProxy
{suu-info}
* You will need to modify the same file on both load balancer nodes.
* Both load balancer nodes need to have the appropriate firewall rules in place to get to your servers before this point.
* You should also know the front-facing ipaddress that your service will be using for this step.
{suu-info}
*Edit {{/etc/haproxy/haproxy.cfg}} (on both nodes)*

You will be adding a new server farm. Here is an example farm.

{code}
listen  api-webfarm 134.250.12.142:8000
        mode http
        balance roundrobin
        option httpclose
        option forwardfor
        option httpchk GET /banner
        server api1 134.250.5.24:8080 maxconn 1 check
        server api2 134.250.5.25:8080 maxconn 1 check
{code}
(!) The listen port must be unique, so if 8000 and 8001 are taken, use 8002

*Restart haproxy*
{code}
sudo /etc/init.d/haproxy restart
{code}

*Commit your changes*
{code}
cd /etc/haproxy/
sudo hg commit -m "New server config."
{code}

{suu-tip}
At this point, you should be able to see if HAProxy thinks your service is up or down by going to:
http://halb1.suu.edu:8001
http://halb2.suu.edu:8001
{suu-tip}

h2. Setup Apache
{suu-info}
* The same configuration will go on both load balander nodes, however, they are not exactly the same. IP addresses will be different.
* You can probably use an existing apache virtual host config file as a starting point. All you really need to do is then change ipaddresses and ports. No need to change the ssl settings because we are using our wildcard certificate.
{suu-info}

# Create a new virtual host configuration
{code}
sudo cp /etc/apache2/sites-available/api-ssl /etc/apache2/sites-available/yourservice-ssl
{code}
# Modify yourservice-ssl
{code}
sudo vim /etc/apache2/sites-available/yourservice-ssl
# Edit the ipaddress ie &lt;VirtualHost 134.250.12.141:443&gt; This should be the front-facing ipaddress for your application. The one that users will be connecting to.
# Edit just the ports in ProxyPass and ProxyPassReverse. The ports would be the haproxy ports you configured in the HAProxy step above.
{code}
# Enable your new virtual host
{code}
sudo a2ensite yourservice-ssl
{code}
# Reload apache
{code}
sudo /etc/init.d/apache2 reload
{code}
# Commit your changes
{code}
cd /etc/apache2/sites-available/
sudo hg add yourservice-ssl
sudo hg commit -m "New virtual host config file."
{code}
# Now do the same thing on the other load balancer node, but make sure the IP addresses for the *{{ProxyPass}}* and *{{ProxyPassReverse}}* are set to the IP address of that node.

h2. Setup your front-facing ipaddress
{suu-info}
* This step only needs to be done on one of the load balancer nodes. It will be automatically replicated to the second node.
* What you are doing here is setting up the ipaddress that users will hit. It is a shared ipaddress between the two nodes. This configuration is handled by Pacemaker
{suu-info}

{suu-tip}
*Tip:*
The following commands only need to be run on one node. They will be replicated automatically to the second node.
*api_ip* - is just the name we came up with to name this ip resource. This one is for the ip that will be used for api.suu.edu
*eth0" - the nic we want this ip to use.
{suu-tip}

# *Setup ipaddress resource*
{code}
sudo crm configure
crm(live)configure# primitive api_ip IPaddr params ip=134.250.12.141 cidr_netmask="255.255.255.0" nic="eth0"
crm(live)configure# commit
crm(live)configure# exit
{code}
# *Set a preferred node for the ip resource*
This tells Pacemaker which node the resource ip should live on when both nodes are up.
{code}
sudo crm configure
crm(live)configure# location api_ip_pref api_ip 100: halb1
crm(live)configure# commit
crm(live)configure# exit
{code}
# *Setup Pacemaker monitoring*
{code}
sudo crm configure
crm(live)configure# monitor api_ip 40s:20s
crm(live)configure# commit
crm(live)configure# exit
{code}
# *Show running configuration*
{code}
sudo crm configure show
{code}

{suu-tip}
At this point, you should be able to hit your service on your front-facing ipaddress port 443 and get a response from your service.
{suu-tip}</property>
    

<property name="body">&lt;ac:macro ac:name="suu-info"&gt;&lt;ac:rich-text-body&gt;
&lt;p&gt;Documentation for managing a firewall on an Ubuntu box.&lt;/p&gt;&lt;/ac:rich-text-body&gt;&lt;/ac:macro&gt;


&lt;h2&gt;Overview&lt;/h2&gt;

&lt;p&gt;One of the simplest ways to manage a firewall on Ubuntu is to use the command &lt;strong&gt;&lt;code&gt;ufw&lt;/code&gt;&lt;/strong&gt;. It stands for &amp;quot;uncomplicated firewall&amp;quot; and it is installed by default. The firewall is not running by default though.&lt;/p&gt;

&lt;h2&gt;Initial Setup&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Set default policy to deny&lt;/strong&gt;&lt;/p&gt;
&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="5d24a6d8-898f-4352-859b-169b551bd847"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
sudo ufw default deny
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;

&lt;p&gt;&lt;strong&gt;Turn on the firewall&lt;/strong&gt;&lt;/p&gt;
&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="c282e371-0262-4fed-a7f5-6f071da5bc7b"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
sudo ufw enable
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;

&lt;h2&gt;Some sample rules&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Allow a specific IP address on any port.&lt;/strong&gt;&lt;/p&gt;
&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="d6e8c6b5-66e2-4767-a3bd-0de29e20072e"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
sudo ufw allow from 134.250.4.188
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;

&lt;p&gt;&lt;strong&gt;Allow a subnet range to a specific port&lt;/strong&gt;&lt;/p&gt;
&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="7ebe3701-13eb-4671-98f5-a9dce23ec231"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
# This allows ssh access from the VPN subnet.
sudo ufw allow from 134.250.236.0/24 to any port 22
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;

&lt;p&gt;&lt;strong&gt;Block a specific IP&lt;/strong&gt;&lt;/p&gt;
&lt;ac:structured-macro ac:name="code" ac:schema-version="1" ac:macro-id="61c5b54b-ff47-49eb-8fb5-62d1fa0164b3"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
sudo ufw deny 134.250.4.77
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;</property>
    

<property name="body">{suu-info}
Documentation for managing a firewall on an Ubuntu box.
{suu-info}


h2. Overview

One of the simplest ways to manage a firewall on Ubuntu is to use the command *{{ufw}}*. It stands for "uncomplicated firewall" and it is installed by default. The firewall is not running by default though.

h2. Initial Setup

*Set default policy to deny*
{code}
sudo ufw default deny
{code}

*Turn on the firewall*
{code}
sudo ufw enable
{code}

h2. Some sample rules

*Allow a specific IP address on any port.
{code}
sudo ufw allow from 134.250.4.188
{code}

*Allow a subnet range to a specific port*
{code}
# This allows ssh access from the VPN subnet.
sudo ufw allow from 134.250.236.0/24 to any port 22
{code}</property>
    

<property name="body">h4. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}


h2. Configuring Automatic Startup
Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
#export LANG=en_US;
#export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
FOR UBUNTU SERVER:

chmod 755 suu_tivoli
update-rc.d suu_tivoli defaults

FOR RED HAT:
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc
It will prompt you for your nodename and password.  Once you have entered them, it will drop you at a tsm&gt; prompt.
You can then type 'backup', no quotes, and it will start an incremental backup.  If you don't want to start one right away,
just type 'quit', no quotes, and it will drop you back at the linux prompt.
To start the daemon, run the following command:

#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Server Notes

{code}
Installing TSM Client V5.5.2 on Ubuntu 9.04 Server 64-bit

Note: These instructions are based on the report "TSM-Client unter Debian/etch einrichten" at "https://wiki.gw.dg.de/index.php/TSM:debian"



1) get the latest client - modify version numbers as needed
wget "ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v5r5/Linux/LinuxX86/v553/5.5.3.0-TIV-TSMBAC-LinuxX86.tar"

** NOTE - execute "sudo su -" prior to running the following build and install.  Otherwise, permissions get jacked

2) apt-get install alien ksh ia32-libs gawk

3) unpack the archive
tar xvf 5.5.3.0-TIV-TSMBAC-LinuxX86.tar

4) unpack the RPM archives (ignore warnings re scripts)
alien -g TIVsm-API.i386.rpm
alien -g TIVsm-BA.i386.rpm

5) change directory names
mv TIVsm-API-5.5.3/debian TIVsm-API-5.5.3/DEBIAN
mv TIVsm-BA-5.5.3/debian TIVsm-BA-5.5.3/DEBIAN

6) edit the control files

vi TIVsm-API-5.5.3/DEBIAN/control
Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-api
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-api
Architecture: amd64
Depends:
Description: the API IBM Tivoli Storage Manager API
Version: 5.5.3
&lt;blank line&gt;

Save and exit the file.

vi TIVsm-BA-5.5.3/DEBIAN/control

Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-ba
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-ba
Architecture: amd64
Depends:
Description: the Backup Archive Client IBM Tivoli Storage Manager Client
Version: 5.5.3
&lt;blank line&gt;

Save and exit the file

7) create *.deb packages
dpkg -b TIVsm-API-5.5.3
dpkg -b TIVsm-BA-5.5.3

8) install *.deb packages
dpkg -i TIVsm-API-5.5.3.deb
dpkg -i TIVsm-BA-5.5.3.deb

9)
cd /tmp
wget [http://security.ubuntu.com/ubuntu/pool/universe/i/ia32-libs/ia32-libs_20090808ubuntu9_amd64.deb]
dpkg-deb \-x ia32-libs_20090808ubuntu9_amd64.deb ia32-libs
sudo cp ia32-libs/usr/lib32/libstdc++.so.5.0.7 /usr/lib32/
cd /usr/lib32
sudo ln \-s libstdc\++.so.5.0.7 libstdc+\+.so.5
10) create/modify TSM configuration files
 (use examples listed above)
vi /opt/tivoli/tsm/client/ba/bin/dsm.opt
vi /opt/tivoli/tsm/client/ba/bin/dsm.sys

11) Run the "Error loading shared libraries" fix located above; run the "English message repository not found" fix as well

12) Link the necessary shared libraries:
add the dsm binary path on a line in the file /etc/ld.so.conf
/opt/tivoli/tsm/client/api/bin
import the shared objects using the command
ldconfig
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/EN_US/

13) run an incremental backup
dsmc incremental

14) start the TSM scheduler
#/etc/init.d/suu_tivoli start
{code}</property>
    

<property name="body">h4. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}


h2. Configuring Automatic Startup
Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
#export LANG=en_US;
#export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
FOR UBUNTU SERVER:

chmod 775 suu_tivoli
update-rc.d suu_tivoli defaults

FOR RED HAT:
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc
It will prompt you for your nodename and password.  Once you have entered them, it will drop you at a tsm&gt; prompt.
You can then type 'backup', no quotes, and it will start an incremental backup.  If you don't want to start one right away,
just type 'quit', no quotes, and it will drop you back at the linux prompt.
To start the daemon, run the following command:

#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
/usr/local/ibm/gsk8/lib
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Server Notes

{code}
Installing TSM Client V6.6.2 on Ubuntu 10.04 Server 64-bit



1) get the latest client - modify version numbers as needed
wget "ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v5r5/Linux/LinuxX86/v553/5.5.3.0-TIV-TSMBAC-LinuxX86.tar"

** NOTE - execute "sudo su -" prior to running the following build and install.  Otherwise, permissions get jacked

2) apt-get install alien ksh ia32-libs gawk

3) unpack the archive
tar xvf 5.5.3.0-TIV-TSMBAC-LinuxX86.tar

4) unpack the RPM archives (ignore warnings re scripts)
alien -g TIVsm-API.i386.rpm
alien -g TIVsm-BA.i386.rpm

5) change directory names
mv TIVsm-API-5.5.3/debian TIVsm-API-5.5.3/DEBIAN
mv TIVsm-BA-5.5.3/debian TIVsm-BA-5.5.3/DEBIAN

6) edit the control files

vi TIVsm-API-5.5.3/DEBIAN/control
Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-api
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-api
Architecture: amd64
Depends:
Description: the API IBM Tivoli Storage Manager API
Version: 5.5.3
&lt;blank line&gt;

Save and exit the file.

vi TIVsm-BA-5.5.3/DEBIAN/control

Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-ba
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-ba
Architecture: amd64
Depends:
Description: the Backup Archive Client IBM Tivoli Storage Manager Client
Version: 5.5.3
&lt;blank line&gt;

Save and exit the file

7) create *.deb packages
dpkg -b TIVsm-API-5.5.3
dpkg -b TIVsm-BA-5.5.3

8) install *.deb packages
dpkg -i TIVsm-API-5.5.3.deb
dpkg -i TIVsm-BA-5.5.3.deb

9)

10) create/modify TSM configuration files
 (use examples listed above)
vi /opt/tivoli/tsm/client/ba/bin/dsm.opt
vi /opt/tivoli/tsm/client/ba/bin/dsm.sys


12) Link the necessary shared libraries:
add the dsm binary path on a line in the file /etc/ld.so.conf
/opt/tivoli/tsm/client/api/bin
import the shared objects using the command
ldconfig
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/EN_US/

13) run an incremental backup
dsmc incremental

14) start the TSM scheduler
#/etc/init.d/suu_tivoli start
{code}</property>
    

<property name="body">h2. Install Apache 

{code} 
sudo apt-get install apache2 libapache2-mod-proxy-html 
a2enmod ssl 
a2enmod proxy 
{code} 

h2. Apache SSL 

Get our wildcard certificate and private key. 

{code} 
sudo mv server.crt /etc/ssl/certs/suu_edu.crt 
sudo mv server.key /etc/ssl/private/suu_edu.key 
{code} 

h2. Configure Apache Virtual Host 

{code} 
cd /etc/apache2/sites-available/ 
sudo cp default-ssl api-ssl 
sudo vim api-ssl 
# 
{code} 

h2. Install HAProxy 

# http://www.zivtech.com/blog/setting-ip-failover-heartbeat-and-pacemaker-ubuntu-lucid 

{code} 
sudo apt-get install haproxy 
{code} 

h2. Install heartbeat and pacemaker 

{code} 
sudo apt-get install heartbeat pacemaker 
{code} 

*Create ha.cf file (main heartbeat config file)* 
{code} 
sudo vim /etc/ha.d/ha.cf 
# Add the following 
autojoin none 
bcast eth0 
warntime 5 
deadtime 15 
initdead 60 
keepalive 2 
node halb1 
node halb2 
crm respawn 
{code} 

*Create authkeys file for heartbeat* 
The following run as a shell script will generate the key, create the authkeys file and set proper permissions on the file. 
{code} 
#!/bin/bash 
( echo -ne "auth 1\n1 sha1 "; \ 
dd if=/dev/urandom bs=512 count=1 | openssl md5 ) \ 
&gt; /etc/ha.d/authkeys 
chmod 0600 /etc/ha.d/authkeys 
{code} 

*Restart heartbeat* 
{code} 
sudo /etc/init.d/heartbeat restart 
{code} 

*Verify that they are online* 
{code} 
sudo crm_mon -1 | grep Online 
{code} 

*Configure shared IPAddress* 
This is part of Pacemaker. To Pacemaker, an ipaddress is a resource. 

{suu-tip} 
*Tip:* 
The following commands only need to be run on one node. They will be replicated automatically to the second node. 
*api_ip* - is just the name we came up with to name this ip resource. This one is for the ip that will be used for api.suu.edu 
*eth0" - the nic we want this ip to use. 
{suu-tip} 

{code} 
sudo crm configure property stonith-enabled=false 
sudo crm configure 
crm(live)configure# primitive api_ip IPaddr params ip=134.250.12.141 cidr_netmask="255.255.255.0" nic="eth0" 
crm(live)configure# commit 
crm(live)configure# exit 
{code} 

*Set a preferred node for the ip resource* 
This tells Pacemaker which node the resource ip should live on when both nodes are up. 
{code} 
sudo crm configure 
crm(live)configure# location api_ip_pref api_ip 100: halb1 
crm(live)configure# commit 
crm(live)configure# exit 
{code} 

*Setup Pacemaker monitoring* 
{code} 
sudo crm configure 
crm(live)configure# monitor api_ip 15s:5s 
crm(live)configure# commit 
crm(live)configure# exit 
{code} 

*Show running configuration* 
{code} 
sudo crm configure show 
{code} </property>
    

<property name="body">h2. Install Apache 

{code} 
sudo apt-get install apache2 libapache2-mod-proxy-html 
a2enmod ssl 
a2enmod proxy 
{code} 

h2. Apache SSL 

Get our wildcard certificate and private key. 

{code} 
sudo mv server.crt /etc/ssl/certs/suu_edu.crt 
sudo mv server.key /etc/ssl/private/suu_edu.key 
{code} 

h2. Configure Apache Virtual Host 

{code} 
cd /etc/apache2/sites-available/ 
sudo cp default-ssl api-ssl 
sudo vim api-ssl 
# 
{code} 

h2. Install HAProxy 

# http://www.zivtech.com/blog/setting-ip-failover-heartbeat-and-pacemaker-ubuntu-lucid 

{code} 
sudo apt-get install haproxy 
{code} 

h2. Install heartbeat and pacemaker 

{code} 
sudo apt-get install heartbeat pacemaker 
{code} 

*Create ha.cf file (main heartbeat config file)* 
{code} 
sudo vim /etc/ha.d/ha.cf 
# Add the following 
autojoin none 
bcast eth0 
warntime 5 
deadtime 15 
initdead 60 
keepalive 2 
node halb1 
node halb2 
crm respawn 
{code} 

h2. Modify /etc/default/haproxy file
{code}
ENABLED=1
{code}
*Create authkeys file for heartbeat*  (original node only)
The following run as a shell script will generate the key, create the authkeys file and set proper permissions on the file. 
{code} 
#!/bin/bash 
( echo -ne "auth 1\n1 sha1 "; \ 
dd if=/dev/urandom bs=512 count=1 | openssl md5 ) \ 
&gt; /etc/ha.d/authkeys 
chmod 0600 /etc/ha.d/authkeys 
{code}
If this is an addtional node, simply copy the authkeys from the original server to your new node

*Restart heartbeat* 
{code} 
sudo /etc/init.d/heartbeat restart 
{code} 

*Verify that they are online* 
{code} 
sudo crm_mon -1 | grep Online 
{code} 

*Configure shared IPAddress* 
This is part of Pacemaker. To Pacemaker, an ipaddress is a resource. 

{suu-tip} 
*Tip:* 
The following commands only need to be run on one node. They will be replicated automatically to the second node. 
*api_ip* - is just the name we came up with to name this ip resource. This one is for the ip that will be used for api.suu.edu 
*eth0" - the nic we want this ip to use. 
{suu-tip} 

{code} 
sudo crm configure property stonith-enabled=false 
sudo crm configure 
crm(live)configure# primitive api_ip IPaddr params ip=134.250.12.141 cidr_netmask="255.255.255.0" nic="eth0" 
crm(live)configure# commit 
crm(live)configure# exit 
{code} 

*Set a preferred node for the ip resource* 
This tells Pacemaker which node the resource ip should live on when both nodes are up. 
{code} 
sudo crm configure 
crm(live)configure# location api_ip_pref api_ip 100: halb1 
crm(live)configure# commit 
crm(live)configure# exit 
{code} 

*Setup Pacemaker monitoring* 
{code} 
sudo crm configure 
crm(live)configure# monitor api_ip 15s:5s 
crm(live)configure# commit 
crm(live)configure# exit 
{code} 

*Show running configuration* 
{code} 
sudo crm configure show 
{code} </property>
    

<property name="body">Similar to Windows Software Update Services, apt-mirror allows us to store a local copy of the Ubuntu updates repository so our machines don't all have to go out to the internet for updates. &amp;nbsp;Not only does this reduce our bandwidth usage, but updates are delivered extremely quickly over local wire. &amp;nbsp;Here is an example of an /etc/apt/sources.list file from an Ubuntu 10.04 LTS 32-bit server install, pointed at our local repository on sherpa.suu.edu:

{code}

deb http://sherpa.suu.edu/ubuntu/ lucid main restricted

## Major bug fix updates produced after the final release of the
## distribution.
deb http://sherpa.suu.edu/ubuntu/ lucid-updates main restricted

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://sherpa.suu.edu/ubuntu/ lucid universe
deb http://sherpa.suu.edu/ubuntu/ lucid-updates universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu 
## team, and may not be under a free licence. Please satisfy yourself as to 
## your rights to use the software. Also, please note that software in 
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://sherpa.suu.edu/ubuntu/ lucid multiverse
deb http://sherpa.suu.edu/ubuntu/ lucid-updates multiverse

## Uncomment the following line to add software from Canonical's
## 'partner' repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
## respective vendors as a service to Ubuntu users.
deb http://sherpa.suu.edu/ubuntupartner lucid partner

## Security Updates
deb http://sherpa.suu.edu/updates lucid-security main restricted
deb http://sherpa.suu.edu/updates lucid-security universe
deb http://sherpa.suu.edu/updates lucid-security multiverse

{code}

NOTE:  We do not currently mirror the deb-src (sources) files, since we rarely if ever compile our packages from source.  Adding these sources to every subsection listed here would more than double the required space to store them.  Your original sources.list file may or may not reference the source repositories.  If it does, you should remove the lines from your file, or at least comment them out.  If you need them, the only solution at this time is to leave them pointed at the original ubuntu location.
</property>
    

<property name="body">&lt;h1&gt;Resizing Logical Volumes&lt;/h1&gt;

&lt;p&gt;This is a continuation of my earlier post. Here I will explain how to resize an existing logical volume. Logical volumes may be resized dynamically while preserving the data on the volume. Here is how:&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;Reducing a logical volume.&lt;/li&gt;
	&lt;li&gt;Reduce the filesystem residing on the logical volume.&lt;/li&gt;
	&lt;li&gt;Reduce the logical volume.&lt;/li&gt;
&lt;/ol&gt;


&lt;p&gt;For different file systems,it is achieved differently.&lt;/p&gt;

&lt;p&gt;For ext2 filesystem&lt;br /&gt;
If you are using LVM 1, then both the above steps could be acomplished by executing a single utility called e2fsadm.&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;umount /data&lt;/li&gt;
	&lt;li&gt;e2fsadm -L -1G /dev/my_vol_grp/my_logical_vol&lt;/li&gt;
	&lt;li&gt;mount /data&lt;br /&gt;
The above command first reduces the filesystem in the 'my_logical_vol'by 1 GB and then reduces themy_logical_vol itself by the same amount.&lt;br /&gt;
If you are using LVM 2 - more recent linux distributions like Fedora use LVM 2 - then you do not have the'e2fsadm' utility. So you have to first reduce the filesystem using 'resize2fs' and then reduce the logical volume using 'lvreduce'.&lt;/li&gt;
	&lt;li&gt;umount /data&lt;/li&gt;
	&lt;li&gt;resize2fs  /dev/my_vol_grp/my_logical_vol  1G&lt;/li&gt;
	&lt;li&gt;lvreduce  -L  1G  /dev/my_vol_grp/my_logical_vol&lt;/li&gt;
	&lt;li&gt;mount /data&lt;br /&gt;
In the above case, I have reduced my file&lt;/li&gt;
	&lt;li&gt;Grow a Logical Volume&lt;br /&gt;
The steps for growing a logical volume are the exact opposite of those for shrinking the logical volume.&lt;/li&gt;
	
	&lt;li&gt;Then resize the filesystem to the new size of your logical volume.&lt;/li&gt;
&lt;/ol&gt;
</property>
    

<property name="body">[|http://linuxhelp.blogspot.com/]
* [Book Reviews|http://linuxhelp.blogspot.com/2006/06/book-reviews-linux-programming-web.html]
* [OS Reviews|http://linuxhelp.blogspot.com/2006/06/operating-system-reviews.html]
* [Ubuntu|http://linuxhelp.blogspot.com/2008/09/ubuntu-articles.html]
* [Contact Me|http://linuxhelp.blogspot.com/p/contact.html]
{color:#666666}April 23, 2005{color}

h1. [Resizing Logical Volumes|http://linuxhelp.blogspot.com/2005/04/resizing-logical-volumes.html]

{color:#222222}T{color}{color:#222222}his is a continuation of my earlier post&amp;nbsp;{color}[Creating Logical Volumes in Linux|http://linuxhelp.blogspot.com/2005/04/creating-lvm-in-linux.html]{color:#222222}&amp;nbsp;. Here I will explain how to resize an existing logical volume. Logical volumes may be resized dynamically while preserving the data on the volume. Here is how:{color}
{color:#000099}Reducing a logical volume{color}
# {color:#222222}Reduce the filesystem residing on the logical volume.{color}
# {color:#222222}Reduce the logical volume.{color}

{color:#222222}For different file&amp;nbsp;{color}{color:#009900 !important}systems{color}{color:#009900 !important}&amp;nbsp;{color}{color:#222222}, it is achieved differently.{color}

{color:#222222}{*}For&amp;nbsp;*{color}{color:#222222}{*}ext2{*}{color}{color:#222222}*&amp;nbsp;file&amp;nbsp;system{*}{color}
{color:#222222}If you are using LVM 1, then both the above steps could be acomplished by executing a single utility called e2fsadm.{color}# umount /data
# e2fsadm -L -1G /dev/my_vol_grp/my_logical_vol
# mount /data
{color:#222222}The above command first reduces the filesystem in the '{color}{color:#222222}my_logical_vol{color}{color:#222222}'&amp;nbsp;{color}{color:#222222}{*}by{*}{color}{color:#222222}&amp;nbsp;1 GB and then reduces the&amp;nbsp;{color}{color:#222222}my_logical_vol{color}{color:#222222}&amp;nbsp;itself by the same amount.{color}
{color:#222222}If you are using LVM 2 - more recent linux distributions like Fedora use LVM 2 - then you do not have the{color}{color:#222222}'e2fsadm{color}{color:#222222}' utility. So you have to first reduce the filesystem using '{color}{color:#222222}{*}resize2fs{*}{color}{color:#222222}' and then reduce the logical volume using '{color}{color:#222222}{*}lvreduce{*}{color}{color:#222222}'.{color}# umount /data
# resize2fs  /dev/my_vol_grp/my_logical_vol  1G
# lvreduce  -L  1G  /dev/my_vol_grp/my_logical_vol
# mount /data
{color:#222222}In the above case, I have reduced my file&amp;nbsp;{color}{color:#009900 !important}system{color}{color:#009900 !important}&amp;nbsp;{color}{color:#222222}&amp;nbsp;"{color}{color:#222222}{*}to{*}{color}{color:#222222}" 1 GB size ...{color}
{color:#ff0000}Note:{color}{color:#222222}&amp;nbsp;I didn't use the minus ({color}{color:#000099}*\-*{color}{color:#222222}) sign while using resize2fs&amp;nbsp;{color}
{color:#222222}... And then used the&amp;nbsp;{color}{color:#222222}{*}lvreduce{*}{color}{color:#222222}&amp;nbsp;command to reduce the logical volume "{color}{color:#222222}{*}to{*}{color}{color:#222222}" 1 GB. If I want to reduce the logical volume "{color}{color:#222222}{*}by{*}{color}{color:#222222}" 1 GB, then I give the same command but with "{color}{color:#222222}*\-L{*}{color}{color:#222222}&amp;nbsp;{color}{color:#990000}*\-*{color}{color:#222222}{*}1G{*}{color}{color:#222222}" instead of "-L 1G".{color}
{color:#000000}{*}Reiserfs file&amp;nbsp;system{*}{color}
{color:#222222}If you have a reiserfs filesystem, then the commands are a bit different than ext2(3).{color}# umount /data
# resize_reiserfs -s -1G /dev/my_vol_grp/my_logical_vol
# lvreduce -L -1G /dev/my_vol_grp/my_logical_vol
# mount -t reiserfs /data
{color:#000000}{*}XFS and JFS filesystems{*}{color}
{color:#222222}As of now, there is no way to shrink these filesystems residing on logical volumes.{color}
{color:#000099}Grow a Logical Volume{color}
{color:#222222}The steps for growing a logical volume are the exact opposite of those for shrinking the logical volume.{color}
# {color:#009900 !important}Enlarge{color}{color:#009900 !important}&amp;nbsp;{color}{color:#222222}&amp;nbsp;the logical volume first.{color}
# {color:#222222}Then resize the filesystem to the new size of your logical volume.{color}</property>
    

<property name="body">&lt;h2&gt;Check the location of all resources&lt;/h2&gt;&lt;ac:structured-macro ac:macro-id="3a7c9343-fa76-4e01-be17-015858e5d649" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[sudo crm_mon -1
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;h2&gt;Migrate a resource to another node&lt;/h2&gt;&lt;ac:structured-macro ac:macro-id="828c387a-a76e-41bf-b5a3-e9507b3c66db" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[sudo crm_resource -M -r api_ip -H halb2
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;h2&gt;Move a resource back to its normal location&lt;/h2&gt;&lt;ac:structured-macro ac:macro-id="b74004d9-c22a-4f99-9f09-4205a1900a46" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[crm_resource -U -r api_ip
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;h2&gt;List resources&lt;/h2&gt;&lt;ac:structured-macro ac:macro-id="53ebdb5e-9bdb-4286-8681-5ae942e508da" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[crm_resource --list]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;h2&gt;Stop a running resource and everything that depends on it (in order to delete it)&lt;/h2&gt;&lt;ac:structured-macro ac:macro-id="24bd40fe-f568-42aa-829f-3307c71647f5" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[ crm_resource --resource &lt;resource_name_from_list&gt; --set-parameter target-role --meta --parameter-value Stopped]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;h2&gt;Check status of sticky table (must have haproxy.stat entry in haproxy.config)&lt;/h2&gt;&lt;ac:structured-macro ac:macro-id="a99556bb-9cef-4f20-8e84-31d58a6deca7" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[(Returned IP address removed for security)
#socat readline /var/run/haproxy.stat
prompt
&gt;set timeout cli 1d

&gt;show table
# table: banner-prod-inb, type: ip, size:512000, used:152

&gt;show table banner-prod-inb
# table: banner-prod-inb, type: ip, size:512000, used:1
0x130df64: key=134.250.x.x use=0 exp=23192485 server_id=1
 
## TO CLEAR STICKY ENTRIES
&gt;clear table banner-inb-prod]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;h2&gt;Delete a resource&lt;/h2&gt;&lt;ac:structured-macro ac:macro-id="0bbfcb02-2951-4caf-9954-fc3e20bc159f" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[crm_resource -D -r my_first_ip -t primitive]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;</property>
    

<property name="body">

h2. Check the location of a resource
{code}
sudo crm_resource -W -r api_ip
{code}

h2. Migrate a resource to another node
{code}
sudo crm_resource -M -r api_ip -H halb2
{code}</property>
    

<property name="body">&lt;h3&gt;/etc/httpd/conf.d/ssl.conf&lt;/h3&gt;
&lt;ac:structured-macro ac:macro-id="98b5afdd-9c9f-4ea0-bca5-ef42db46274b" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
#   SSL Cipher Suite:
# List the ciphers that the client is permitted to negotiate.
# See the mod_ssl documentation for a complete list.
SSLCipherSuite ALL:!aNULL:!ADH:!eNULL:!LOW:!EXP:RC4+RSA:+HIGH:+MEDIUM

#   Server Certificate:
# Point SSLCertificateFile at a PEM encoded certificate.  If
# the certificate is encrypted, then you will be prompted for a
# pass phrase.  Note that a kill -HUP will prompt again.  A new
# certificate can be generated using the genkey(1) command.
SSLCertificateFile /etc/pki/tls/certs/suucert.pem

#   Server Private Key:
#   If the key is not combined with the certificate, use this
#   directive to point at the key file.  Keep in mind that if
#   you've both a RSA and a DSA private key you can configure
#   both in parallel (to also allow the use of DSA ciphers, etc.)
SSLCertificateKeyFile /etc/pki/tls/private/suuprivate.key

#   Server Certificate Chain:
#   Point SSLCertificateChainFile at a file containing the
#   concatenation of PEM encoded CA certificates which form the
#   certificate chain for the server certificate. Alternatively
#   the referenced file can be the same as SSLCertificateFile
#   when the CA certificates are directly appended to the server
#   certificate for convinience.
#SSLCertificateChainFile /etc/pki/tls/certs/

#   Certificate Authority (CA):
#   Set the CA certificate verification path where to find CA
#   certificates for client authentication or alternatively one
#   huge file containing all of them (file must be PEM encoded)
SSLCACertificateFile /etc/pki/tls/certs/RapidRoot.pem
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;

&lt;h3&gt;/etc/httpd/conf/httpd.conf&lt;/h3&gt;
&lt;p&gt;Be sure the following Trace directive exists in your global config section&lt;/p&gt;
&lt;ac:structured-macro ac:macro-id="772eb1c9-11b7-4f53-83f2-2a823f563b4b" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[
### Section 1: Global Environment
#
# The directives in this section affect the overall operation of Apache,
# such as the number of concurrent requests it can handle or where it
# can find its configuration files.
#
TraceEnable off
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;</property>
    

<property name="body">h3. /etc/httpd/conf.d/ssl.conf
&lt;code&gt;
#   SSL Cipher Suite:
# List the ciphers that the client is permitted to negotiate.
# See the mod_ssl documentation for a complete list.
SSLCipherSuite ALL:!ADH:!EXPORT:!SSLv2:RC4+RSA:+HIGH:+MEDIUM:+LOW

#   Server Certificate:
# Point SSLCertificateFile at a PEM encoded certificate.  If
# the certificate is encrypted, then you will be prompted for a
# pass phrase.  Note that a kill -HUP will prompt again.  A new
# certificate can be generated using the genkey(1) command.
SSLCertificateFile /etc/pki/tls/certs/suucert.pem

#   Server Private Key:
#   If the key is not combined with the certificate, use this
#   directive to point at the key file.  Keep in mind that if
#   you've both a RSA and a DSA private key you can configure
#   both in parallel (to also allow the use of DSA ciphers, etc.)
SSLCertificateKeyFile /etc/pki/tls/private/suuprivate.key

#   Server Certificate Chain:
#   Point SSLCertificateChainFile at a file containing the
#   concatenation of PEM encoded CA certificates which form the
#   certificate chain for the server certificate. Alternatively
#   the referenced file can be the same as SSLCertificateFile
#   when the CA certificates are directly appended to the server
#   certificate for convinience.
#SSLCertificateChainFile /etc/pki/tls/certs/

#   Certificate Authority (CA):
#   Set the CA certificate verification path where to find CA
#   certificates for client authentication or alternatively one
#   huge file containing all of them (file must be PEM encoded)
SSLCACertificateFile /etc/pki/tls/certs/RapidRoot.pem
&lt;code&gt;</property>
    

<property name="body">h3. /etc/httpd/conf.d/ssl.conf
&lt;code&gt;
#   SSL Cipher Suite:
# List the ciphers that the client is permitted to negotiate.
# See the mod_ssl documentation for a complete list.
SSLCipherSuite ALL:!aNULL:!ADH:!eNULL:!LOW:!EXP:RC4+RSA:+HIGH:+MEDIUM

#   Server Certificate:
# Point SSLCertificateFile at a PEM encoded certificate.  If
# the certificate is encrypted, then you will be prompted for a
# pass phrase.  Note that a kill -HUP will prompt again.  A new
# certificate can be generated using the genkey(1) command.
SSLCertificateFile /etc/pki/tls/certs/suucert.pem

#   Server Private Key:
#   If the key is not combined with the certificate, use this
#   directive to point at the key file.  Keep in mind that if
#   you've both a RSA and a DSA private key you can configure
#   both in parallel (to also allow the use of DSA ciphers, etc.)
SSLCertificateKeyFile /etc/pki/tls/private/suuprivate.key

#   Server Certificate Chain:
#   Point SSLCertificateChainFile at a file containing the
#   concatenation of PEM encoded CA certificates which form the
#   certificate chain for the server certificate. Alternatively
#   the referenced file can be the same as SSLCertificateFile
#   when the CA certificates are directly appended to the server
#   certificate for convinience.
#SSLCertificateChainFile /etc/pki/tls/certs/

#   Certificate Authority (CA):
#   Set the CA certificate verification path where to find CA
#   certificates for client authentication or alternatively one
#   huge file containing all of them (file must be PEM encoded)
SSLCACertificateFile /etc/pki/tls/certs/RapidRoot.pem
&lt;code&gt;</property>
    

<property name="body">h3. /etc/httpd/conf.d/ssl.conf
&lt;code&gt;
#   SSL Cipher Suite:
# List the ciphers that the client is permitted to negotiate.
# See the mod_ssl documentation for a complete list.
SSLCipherSuite ALL:!aNULL:!ADH:!eNULL:!LOW:!EXP:RC4+RSA:+HIGH:+MEDIUM

#   Server Certificate:
# Point SSLCertificateFile at a PEM encoded certificate.  If
# the certificate is encrypted, then you will be prompted for a
# pass phrase.  Note that a kill -HUP will prompt again.  A new
# certificate can be generated using the genkey(1) command.
SSLCertificateFile /etc/pki/tls/certs/suucert.pem

#   Server Private Key:
#   If the key is not combined with the certificate, use this
#   directive to point at the key file.  Keep in mind that if
#   you've both a RSA and a DSA private key you can configure
#   both in parallel (to also allow the use of DSA ciphers, etc.)
SSLCertificateKeyFile /etc/pki/tls/private/suuprivate.key

#   Server Certificate Chain:
#   Point SSLCertificateChainFile at a file containing the
#   concatenation of PEM encoded CA certificates which form the
#   certificate chain for the server certificate. Alternatively
#   the referenced file can be the same as SSLCertificateFile
#   when the CA certificates are directly appended to the server
#   certificate for convinience.
#SSLCertificateChainFile /etc/pki/tls/certs/

#   Certificate Authority (CA):
#   Set the CA certificate verification path where to find CA
#   certificates for client authentication or alternatively one
#   huge file containing all of them (file must be PEM encoded)
SSLCACertificateFile /etc/pki/tls/certs/RapidRoot.pem
&lt;code&gt;</property>
    

<property name="body">h3. /etc/httpd/conf.d/ssl.conf
&lt;code&gt;
#   SSL Cipher Suite:
# List the ciphers that the client is permitted to negotiate.
# See the mod_ssl documentation for a complete list.
SSLCipherSuite ALL:!aNULL:!ADH:!eNULL:!LOW:!EXP:RC4+RSA:+HIGH:+MEDIUM

#   Server Certificate:
# Point SSLCertificateFile at a PEM encoded certificate.  If
# the certificate is encrypted, then you will be prompted for a
# pass phrase.  Note that a kill -HUP will prompt again.  A new
# certificate can be generated using the genkey(1) command.
SSLCertificateFile /etc/pki/tls/certs/suucert.pem

#   Server Private Key:
#   If the key is not combined with the certificate, use this
#   directive to point at the key file.  Keep in mind that if
#   you've both a RSA and a DSA private key you can configure
#   both in parallel (to also allow the use of DSA ciphers, etc.)
SSLCertificateKeyFile /etc/pki/tls/private/suuprivate.key

#   Server Certificate Chain:
#   Point SSLCertificateChainFile at a file containing the
#   concatenation of PEM encoded CA certificates which form the
#   certificate chain for the server certificate. Alternatively
#   the referenced file can be the same as SSLCertificateFile
#   when the CA certificates are directly appended to the server
#   certificate for convinience.
#SSLCertificateChainFile /etc/pki/tls/certs/

#   Certificate Authority (CA):
#   Set the CA certificate verification path where to find CA
#   certificates for client authentication or alternatively one
#   huge file containing all of them (file must be PEM encoded)
SSLCACertificateFile /etc/pki/tls/certs/RapidRoot.pem
&lt;code&gt;

h3. /etc/httpd/conf/httpd.conf
Be sure the following Trace directive exists in your global config section
&lt;code&gt;
### Section 1: Global Environment
#
# The directives in this section affect the overall operation of Apache,
# such as the number of concurrent requests it can handle or where it
# can find its configuration files.
#
TraceEnable off
&lt;code&gt;</property>
    

<property name="body">{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMMethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu
nodename MARKETPLACE
passwordaccess generate
MANAGEDSERVICES	schedule webclient

include /usr/local/touchnet/.../*
include /home/.../*
include /etc/.../*
exclude.dir /bin
exclude.dir /boot
exclude.dir /dev
exclude.dir /initrd
exclude.dir /lib
exclude.dir /lost*
exclude.dir /media
exclude.dir /mnt
exclude.dir /opt
exclude.dir /proc
exclude.dir /root
exclude.dir /sbin
exclude.dir /srv
exclude.dir /tmp
exclude.dir /var
exclude.dir /usr/bin
exclude.dir /usr/games
exclude.dir /usr/include
exclude.dir /usr/lib
exclude.dir /usr/sbin
exclude.dir /usr/share
exclude.dir /usr/src
exclude.dir /usr/X11R6
exclude.dir /usr/local/bin
exclude.dir /usr/local/etc
exclude.dir /usr/local/games
exclude.dir /usr/local/include
exclude.dir /usr/local/lib
exclude.dir /usr/local/sbin
exclude.dir /usr/local/share
exclude.dir /usr/local/src
{code}</property>
    

<property name="body">h4. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}


h2. Configuring Automatic Startup
Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
#export LANG=en_US;
#export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
FOR UBUNTU SERVER:

chmod 775 suu_tivoli
update-rc.d suu_tivoli defaults

FOR RED HAT:
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc
It will prompt you for your nodename and password.  Once you have entered them, it will drop you at a tsm&gt; prompt.
You can then type 'backup', no quotes, and it will start an incremental backup.  If you don't want to start one right away,
just type 'quit', no quotes, and it will drop you back at the linux prompt.
To start the daemon, run the following command:

#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
/usr/local/ibm/gsk8/lib
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Server Notes

{code}
Installing TSM Client V6.6.2 on Ubuntu 10.04 Server 64-bit



1) get the latest client - modify version numbers as needed
wget "ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v5r5/Linux/LinuxX86/v553/5.5.3.0-TIV-TSMBAC-LinuxX86.tar"

** NOTE - execute "sudo su -" prior to running the following build and install.  Otherwise, permissions get jacked

2) apt-get install alien ksh ia32-libs gawk

3) unpack the archive
tar xvf 5.5.3.0-TIV-TSMBAC-LinuxX86.tar

4) unpack the RPM archives (ignore warnings re scripts)
alien -g TIVsm-API.i386.rpm
alien -g TIVsm-BA.i386.rpm

5) change directory names
mv TIVsm-API-5.5.3/debian TIVsm-API-5.5.3/DEBIAN
mv TIVsm-BA-5.5.3/debian TIVsm-BA-5.5.3/DEBIAN

6) edit the control files

vi TIVsm-API-5.5.3/DEBIAN/control
Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-api
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-api
Architecture: amd64
Depends:
Description: the API IBM Tivoli Storage Manager API
Version: 5.5.3
&lt;blank line&gt;

Save and exit the file.

vi TIVsm-BA-5.5.3/DEBIAN/control

Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-ba
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-ba
Architecture: amd64
Depends:
Description: the Backup Archive Client IBM Tivoli Storage Manager Client
Version: 5.5.3
&lt;blank line&gt;

Save and exit the file

7) create *.deb packages
dpkg -b TIVsm-API-5.5.3
dpkg -b TIVsm-BA-5.5.3

8) install *.deb packages
dpkg -i TIVsm-API-5.5.3.deb
dpkg -i TIVsm-BA-5.5.3.deb

9) mkdir -p /var/lock/subsys
   touch /var/lock/subsys/tivoli

10) create/modify TSM configuration files
 (use examples listed above)
vi /opt/tivoli/tsm/client/ba/bin/dsm.opt
vi /opt/tivoli/tsm/client/ba/bin/dsm.sys


12) Link the necessary shared libraries:
add the dsm binary path on a line in the file /etc/ld.so.conf
/opt/tivoli/tsm/client/api/bin
import the shared objects using the command
ldconfig
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/EN_US/

13) run an incremental backup
dsmc incremental

14) start the TSM scheduler
#/etc/init.d/suu_tivoli start
{code}</property>
    

<property name="body">&lt;h3&gt;Oracle production database servers (Red Hat or CentOS)&lt;/h3&gt;&lt;ac:structured-macro ac:macro-id="854b9aa8-b0d6-45c1-8465-17e4fef39f7b" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername tivoli
   COMMMethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu
nodename &lt;servernamehere&gt;
passwordaccess generate
MANAGEDSERVICES schedule webclient
include /backup/.../*
include /u01/.../*
include /home/.../*
include /etc/.../*
include /root/.../*
exclude dsmsched.log
exclude core
exclude /.../core
exclude /.../tmp/.../*
exclude /.../tmp/*/.../*
exclude /tmp/*/.../*
exclude /.../Cache/*/.../*
exclude /var/run/*/.../*
exclude /var/tmp/*/.../*
exclude.dir /dev
exclude.dir /mnt
exclude.dir /proc
exclude.dir /*/oradata
exclude.dir /var/cache
exclude.dir /usr/src
 ]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;h3&gt;Ubuntu Server&lt;/h3&gt;&lt;ac:structured-macro ac:macro-id="872e7246-a5f7-453f-84d5-71bcc57332de" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************
*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.
*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.
************************************************************************
SErvername  tivoli
   COMMMethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu
nodename WIKI
passwordaccess generate
MANAGEDSERVICES schedule webclient
include /home/.../*
include /etc/.../*
exclude.dir /bin
exclude.dir /boot
exclude.dir /dev
exclude.dir /initrd
exclude.dir /lib
exclude.dir /lost*
exclude.dir /media
exclude.dir /mnt
exclude.dir /opt
exclude.dir /proc
exclude.dir /root
exclude.dir /sbin
exclude.dir /srv
exclude.dir /tmp
exclude.dir /usr/bin
exclude.dir /usr/games
exclude.dir /usr/include
exclude.dir /usr/lib
exclude.dir /usr/sbin
exclude.dir /usr/share
exclude.dir /usr/src
exclude.dir /usr/X11R6
exclude.dir /usr/local/bin
exclude.dir /usr/local/games
exclude.dir /usr/local/include
exclude.dir /usr/local/lib
exclude.dir /usr/local/sbin
exclude.dir /usr/local/share
exclude.dir /usr/local/src
exclude.dir /var/lib]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;</property>
    

<property name="body" />
    

<property name="body">h3. database servers
{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername tivoli
   COMMMethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu
nodename MAHOGANY
passwordaccess generate
MANAGEDSERVICES schedule webclient
include /u01/.../*
include /home/.../*
include /etc/.../*
include /root/.../*
exclude.dir /dev
exclude.dir /mnt
exclude.dir /proc
exclude.dir /*/oradata
exclude.dir /usr/share
{code}</property>
    

<property name="body">h3. database servers
{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername tivoli
   COMMMethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu
nodename MAHOGANY
passwordaccess generate
MANAGEDSERVICES schedule webclient
include /u01/.../*
include /home/.../*
include /etc/.../*
include /root/.../*
exclude.dir /dev
exclude.dir /mnt
exclude.dir /proc
exclude.dir /*/oradata
exclude.dir /usr/share
exclude.dir /usr/src
{code}</property>
    

<property name="body">h3. database servers
{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername tivoli
   COMMMethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu
nodename ADIRONDACK
passwordaccess generate
MANAGEDSERVICES schedule webclient
include /u01/.../*
include /home/.../*
include /etc/.../*
include /root/.../*
exclude.dir /lib
exclude.dir /lib64
exclude.dir /dev
exclude.dir /mnt
exclude.dir /proc
exclude.dir /*/oradata
exclude.dir /usr/include
exclude.dir /usr/share
exclude.dir /usr/src
exclude.dir /usr/lib
exclude.dir /usr/lib64
exclude.dir /var/cache
exclude.dir /usr/src
{code}</property>
    

<property name="body">h3. Oracle database servers
{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername tivoli
   COMMMethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu
nodename ADIRONDACK
passwordaccess generate
MANAGEDSERVICES schedule webclient
include /u01/.../*
include /home/.../*
include /etc/.../*
include /root/.../*
exclude.dir /lib
exclude.dir /lib64
exclude.dir /dev
exclude.dir /mnt
exclude.dir /proc
exclude.dir /*/oradata
exclude.dir /usr/include
exclude.dir /usr/share
exclude.dir /usr/src
exclude.dir /usr/lib
exclude.dir /usr/lib64
exclude.dir /var/cache
exclude.dir /usr/src
{code}</property>
    

<property name="body">h3. Oracle database servers
{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername tivoli
   COMMMethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu
nodename &lt;servernamehere&gt;
passwordaccess generate
MANAGEDSERVICES schedule webclient
include /backup/.../*
include /u01/.../*
include /home/.../*
include /etc/.../*
include /root/.../*
exclude.dir /lib
exclude.dir /lib64
exclude.dir /dev
exclude.dir /mnt
exclude.dir /proc
exclude.dir /*/oradata
exclude.dir /usr/include
exclude.dir /usr/share
exclude.dir /usr/src
exclude.dir /usr/lib
exclude.dir /usr/lib64
exclude.dir /var/cache
exclude.dir /usr/src
{code}</property>
    

<property name="body">h3. Oracle database servers
{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername tivoli
   COMMMethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu
nodename &lt;servernamehere&gt;
passwordaccess generate
MANAGEDSERVICES schedule webclient
include /backup/.../*
include /u01/.../*
include /home/.../*
include /etc/.../*
include /root/.../*
exclude dsmsched.log
exclude core
exclude /.../core
exclude /.../tmp/.../*
exclude *_log
exclude *.log
exclude /tmp/*/.../*
exclude /.../Cache/*/.../*
exclude /var/run/*/.../*
exclude /var/tmp/*/.../*
exclude.dir /lib
exclude.dir /lib64
exclude.dir /dev
exclude.dir /mnt
exclude.dir /proc
exclude.dir /*/oradata
exclude.dir /usr/include
exclude.dir /usr/share
exclude.dir /usr/src
exclude.dir /usr/lib
exclude.dir /usr/lib64
exclude.dir /var/cache
exclude.dir /usr/src
exclude.dir /var/spool/cups/
{code}</property>
    

<property name="body">h3. Oracle production database servers
{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername tivoli
   COMMMethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu
nodename &lt;servernamehere&gt;
passwordaccess generate
MANAGEDSERVICES schedule webclient
include /backup/.../*
include /u01/.../*
include /home/.../*
include /etc/.../*
include /root/.../*
exclude dsmsched.log
exclude core
exclude /.../core
exclude /.../tmp/.../*
exclude *_log
exclude *.log
exclude /tmp/*/.../*
exclude /.../Cache/*/.../*
exclude /var/run/*/.../*
exclude /var/tmp/*/.../*
exclude.dir /lib
exclude.dir /lib64
exclude.dir /dev
exclude.dir /mnt
exclude.dir /proc
exclude.dir /*/oradata
exclude.dir /usr/include
exclude.dir /usr/share
exclude.dir /usr/src
exclude.dir /usr/lib
exclude.dir /usr/lib64
exclude.dir /var/cache
exclude.dir /usr/src
exclude.dir /var/spool/cups/
{code}</property>
    

<property name="body">&lt;h3&gt;How do I tell what is running on a given port?&lt;/h3&gt;&lt;ac:structured-macro ac:macro-id="8d20c2c1-c5f9-43f0-afbf-805f43845588" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[lsof -i :&lt;port number&gt;
i.e. lsof -i :5353
]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;&lt;h3&gt;How do I remove unused kernels on Ubuntu Server?&lt;/h3&gt;&lt;ac:structured-macro ac:macro-id="5f42a257-991c-421a-b094-20fb32e3bdc6" ac:name="code" ac:schema-version="1"&gt;&lt;ac:plain-text-body&gt;&lt;![CDATA[#apt-get autoremove
#apt-get autoclean
#cd /boot
#uname -r (make note of response; this is the running kernel)
2.6.32-40-server
Use regex to remove everything *except* the running kernel.  In my case, the following command did it:
#apt-get remove linux-image-2.6.32-3[0-9]-server
This removed all kernels from version 30-39, leaving just the running one (40) intact.  This freed up 767MB of space.
 ]] &gt;&lt;/ac:plain-text-body&gt;&lt;/ac:structured-macro&gt;</property>
    

<property name="body">{suu-info}
This is the root page for our HAProxy documentation.
{suu-info}

{suu-tip}
*How to check on the status of things*
* *Check status of HAProxy*
** http://halb1.suu.edu:8001
** http://halb2.suu.edu:8001
* *Check the status of the nodes*
** SSH into one of the nodes
{code}
ssh halb1.suu.edu
sudo crm_mon --one-shot -V | grep Online
# The output will look something like this:
Online: [ halb1 halb2 ]
{code}

{suu-tip}


h2. Overview

* We have two load balancer nodes running in a cluster. They are active/active and will automatically take over for the other if one goes down.
* The load balance cluster has multiple shared IP addresses. The shared IP addresses are the user-facing IPs and that is where firewall rules are applied for user access.

Current production setup example: (note we have more stuff behind our load balancers, but this demonstrates the basic idea.)
{code}

        shared IP=12.141
            ^^^^^^^^
       12.142      12.143       5.24  5.25  
 -------+------------+-----------+-----+---
        |            |           |     |   
     +--+--+      +--+--+      +-+-+ +-+-+ 
     | LB1 |      | LB2 |      | A | | B | 
     +-----+      +-----+      +---+ +---+ 
     haproxy      haproxy       web servers
     heartbeat    heartbeat
     pacemaker    pacemaker

{code}
*LB1* = halb1.suu.edu
*LB2* = halb2.suu.edu
*A* = api1.suu.edu
*B* = api2.suu.edu
*shared IP* = api.suu.edu

</property>
    

<property name="body">h4. /&lt;tomcat_home&gt;/conf/Catalina/localhost/manager.xml
{code}
&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0?

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
--&gt;
&lt;!--

Context configuration file for the Tomcat Manager Web App

$Id: manager.xml 562814 2007-08-05 03:52:04Z markt $

--&gt;

&lt;Context docBase="${catalina.home}/webapps/manager" privileged="true" antiResourceLocking="false" antiJARLocking="false"&gt;
&lt;Valve className="org.apache.catalina.valves.RemoteAddrValve" allow="127.0.0.1,134.250.4.*"/&gt;
&lt;/Context&gt;
{code}

h4. /&lt;tomcat_home&gt;/conf/server.xml
{code}
&lt;?xml version='1.0' encoding='utf-8'?&gt;
&lt;!--
  Licensed to the Apache Software Foundation (ASF) under one or more
  contributor license agreements.  See the NOTICE file distributed with
  this work for additional information regarding copyright ownership.
  The ASF licenses this file to You under the Apache License, Version 2.0
  (the "License"); you may not use this file except in compliance with
  the License.  You may obtain a copy of the License at

      http://www.apache.org/licenses/LICENSE-2.0

  Unless required by applicable law or agreed to in writing, software
  distributed under the License is distributed on an "AS IS" BASIS,
  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  See the License for the specific language governing permissions and
  limitations under the License.
--&gt;
&lt;!-- Note:  A "Server" is not itself a "Container", so you may not
     define subcomponents such as "Valves" at this level.
     Documentation at /docs/config/server.html
 --&gt;
&lt;Server port="8005" shutdown="SHUTDOWN"&gt;

  &lt;!--APR library loader. Documentation at /docs/apr.html --&gt;
  &lt;Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" /&gt;
  &lt;!--Initialize Jasper prior to webapps are loaded. Documentation at /docs/jasper-howto.html --&gt;
  &lt;Listener className="org.apache.catalina.core.JasperListener" /&gt;
  &lt;!-- JMX Support for the Tomcat server. Documentation at /docs/non-existent.html --&gt;
  &lt;Listener className="org.apache.catalina.mbeans.ServerLifecycleListener" /&gt;
  &lt;Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" /&gt;

  &lt;!-- Global JNDI resources
       Documentation at /docs/jndi-resources-howto.html
  --&gt;
  &lt;GlobalNamingResources&gt;
    &lt;!-- Editable user database that can also be used by
         UserDatabaseRealm to authenticate users
    --&gt;
    &lt;Resource name="UserDatabase" auth="Container"
              type="org.apache.catalina.UserDatabase"
              description="User database that can be updated and saved"
              factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
              pathname="conf/tomcat-users.xml" /&gt;
  &lt;/GlobalNamingResources&gt;

  &lt;!-- A "Service" is a collection of one or more "Connectors" that share
       a single "Container" Note:  A "Service" is not itself a "Container",
       so you may not define subcomponents such as "Valves" at this level.
       Documentation at /docs/config/service.html
   --&gt;
  &lt;Service name="Catalina"&gt;

    &lt;!--The connectors can use a shared executor, you can define one or more named thread pools--&gt;
    &lt;!--
    &lt;Executor name="tomcatThreadPool" namePrefix="catalina-exec-"
        maxThreads="150" minSpareThreads="4"/&gt;
    --&gt;


    &lt;!-- A "Connector" represents an endpoint by which requests are received
         and responses are returned. Documentation at :
         Java HTTP Connector: /docs/config/http.html (blocking &amp; non-blocking)
         Java AJP  Connector: /docs/config/ajp.html
         APR (HTTP/AJP) Connector: /docs/apr.html
         Define a non-SSL HTTP/1.1 Connector on port 8080
    --&gt;
  &lt;!-- &lt;Connector port="8080" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443" /&gt;  --&gt;
    &lt;!-- A "Connector" using the shared thread pool--&gt;
    &lt;!--
    &lt;Connector executor="tomcatThreadPool"
               port="8080" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443" /&gt;
    --&gt;
    &lt;!-- Define a SSL HTTP/1.1 Connector on port 8443
         This connector uses the JSSE configuration, when using APR, the
         connector should be using the OpenSSL style configuration
         described in the APR documentation --&gt;

    &lt;Connector  port="8443"
                protocol="org.apache.coyote.http11.Http11Protocol"
                ciphers="SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA"
              SSLEnabled="true"
                enableLookups="false"
                disableUploadTimeout="true"
                acceptCount="100"
                maxThreads="200"
                scheme="https"
                secure="true"
                clientAuth="false"
                keystoreFile="/home/touchnet/ssl/keystore.wc"
                keystorePass="&lt;removedforwiki&gt;"
                sslProtocol="TLS"
      /&gt;

    &lt;!-- Define an AJP 1.3 Connector on port 8009 --&gt;
    &lt;Connector port="8009" protocol="AJP/1.3" redirectPort="8443" /&gt;


    &lt;!-- An Engine represents the entry point (within Catalina) that processes
         every request.  The Engine implementation for Tomcat stand alone
         analyzes the HTTP headers included with the request, and passes them
         on to the appropriate Host (virtual host).
         Documentation at /docs/config/engine.html --&gt;

    &lt;!-- You should set jvmRoute to support load-balancing via AJP ie :
    &lt;Engine name="Catalina" defaultHost="localhost" jvmRoute="jvm1"&gt;
    --&gt;
    &lt;Engine name="Catalina" defaultHost="localhost"&gt;

      &lt;!--For clustering, please take a look at documentation at:
          /docs/cluster-howto.html  (simple how to)
          /docs/config/cluster.html (reference documentation) --&gt;
      &lt;!--
      &lt;Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster"/&gt;
      --&gt;

      &lt;!-- The request dumper valve dumps useful debugging information about
           the request and response data received and sent by Tomcat.
           Documentation at: /docs/config/valve.html --&gt;
      &lt;!--
      &lt;Valve className="org.apache.catalina.valves.RequestDumperValve"/&gt;
      --&gt;

      &lt;!-- This Realm uses the UserDatabase configured in the global JNDI
           resources under the key "UserDatabase".  Any edits
           that are performed against this UserDatabase are immediately
           available for use by the Realm.  --&gt;
      &lt;Realm className="org.apache.catalina.realm.UserDatabaseRealm"
             resourceName="UserDatabase" digest="SHA" /&gt;

      &lt;!-- Define the default virtual host
           Note: XML Schema validation will not work with Xerces 2.2.
       --&gt;
      &lt;Host name="localhost"  appBase="webapps"
            unpackWARs="true" autoDeploy="true"
            xmlValidation="false" xmlNamespaceAware="false"&gt;

        &lt;!-- SingleSignOn valve, share authentication between web applications
             Documentation at: /docs/config/valve.html --&gt;
        &lt;!--
        &lt;Valve className="org.apache.catalina.authenticator.SingleSignOn" /&gt;
        --&gt;

        &lt;!-- Access log processes all example.
             Documentation at: /docs/config/valve.html --&gt;
        &lt;!--
        &lt;Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"
               prefix="localhost_access_log." suffix=".txt" pattern="common" resolveHosts="false"/&gt;
        --&gt;

      &lt;/Host&gt;
    &lt;/Engine&gt;
  &lt;/Service&gt;
&lt;/Server&gt;
{code}

h4. /&lt;tomcat_home&gt;/conf/logging.properties
{code}
# Licensed to the Apache Software Foundation (ASF) under one or more
# contributor license agreements.  See the NOTICE file distributed with
# this work for additional information regarding copyright ownership.
# The ASF licenses this file to You under the Apache License, Version 2.0
# (the "License"); you may not use this file except in compliance with
# the License.  You may obtain a copy of the License at
#
#     http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

handlers = 1catalina.org.apache.juli.FileHandler, 2localhost.org.apache.juli.FileHandler, 3manager.org.apache.juli.FileHandler, 4host-manager.org.apache.juli.FileHandler, java.util.logging.ConsoleHandler

.handlers = 1catalina.org.apache.juli.FileHandler, java.util.logging.ConsoleHandler

############################################################
# Handler specific properties.
# Describes specific configuration info for Handlers.
############################################################

1catalina.org.apache.juli.FileHandler.level = WARNING
1catalina.org.apache.juli.FileHandler.directory = ${catalina.base}/logs
1catalina.org.apache.juli.FileHandler.prefix = catalina.

2localhost.org.apache.juli.FileHandler.level = WARNING
2localhost.org.apache.juli.FileHandler.directory = ${catalina.base}/logs
2localhost.org.apache.juli.FileHandler.prefix = localhost.

3manager.org.apache.juli.FileHandler.level = WARNING
3manager.org.apache.juli.FileHandler.directory = ${catalina.base}/logs
3manager.org.apache.juli.FileHandler.prefix = manager.

4host-manager.org.apache.juli.FileHandler.level = WARNING
4host-manager.org.apache.juli.FileHandler.directory = ${catalina.base}/logs
4host-manager.org.apache.juli.FileHandler.prefix = host-manager.

java.util.logging.ConsoleHandler.level = WARNING
java.util.logging.ConsoleHandler.formatter = java.util.logging.SimpleFormatter


############################################################
# Facility specific properties.
# Provides extra control for each logger.
############################################################

org.apache.catalina.core.ContainerBase.[Catalina].[localhost].level = WARNING
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].handlers = 2localhost.org.apache.juli.FileHandler

org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/manager].level = WARNING
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/manager].handlers = 3manager.org.apache.juli.FileHandler

org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/host-manager].level = WARNING
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/host-manager].handlers = 4host-manager.org.apache.juli.FileHandler

# For example, set the com.xyz.foo logger to only log SEVERE
# messages:
#org.apache.catalina.startup.ContextConfig.level = WARNING
#org.apache.catalina.startup.HostConfig.level = WARNING
#org.apache.catalina.session.ManagerBase.level = WARNING
#org.apache.catalina.core.AprLifecycleListener.level=WARNING
{code}</property>
    

<property name="body">h4. Populate /etc/init.d/suu_tomcat
{code}
#!/bin/bash
#
# Startup script for Tomcat server
#
# chkconfig: - 83 53
# description: Starts and stops the Tomcat daemon.
# processname: tomcat
# pidfile: /var/run/tomcat.pid
export JAVA_HOME=/usr/lib/jvm/java-6-sun
export TOMCAT_HOME=&lt;tomcat_home_dir&gt;
export TOMCAT_USER=&lt;tomcat user&gt;

# See how we were called.
case $1 in
        start)

su - $TOMCAT_USER -c "sh $TOMCAT_HOME/bin/startup.sh"
        ;;
        stop)
su - $TOMCAT_USER -c "sh $TOMCAT_HOME/bin/shutdown.sh"
        ;;
        restart)
su - $TOMCAT_USER -c "sh $TOMCAT_HOME/bin/shutdown.sh"
su - $TOMCAT_USER -c "sh $TOMCAT_HOME/bin/startup.sh"
        ;;
        *)
                echo "Usage: /etc/init.d/suu_tomcat start|stop|restart"
        ;;
esac

exit 0
{code}

A couple of things to note here; we 'su' to the user we want the process to run as. This is important because we do NOT want processes running as root. Additionally, we are explicitly setting the JAVA_HOME environment variable here, but you may wish to set it in /etc/profile (system-wide) or \~.bashrc (user-specific).

h4. Set for automatic startup
Run the following as root  (Ubuntu and Red Hat):
{code}
chmod 755 /etc/init.d/suu_tomcat
{code}
Next, run the following as root:
For Red Hat:
{code}
chkconfig --add suu_tomcat
chkconfig --level 345 suu_tomcat on
{code}

For Ubuntu:
{code}
update-rc.d suu_tomcat defaults
{code}

That's it - reboot and make sure it works.</property>
    

<property name="body">{section}

{column:width=50%}

{info:title=Description}
Misc. Linux documentation. When we find something useful regarding Linux that we might use again, it should get documented here.
{info}

{livesearch:id=1|spaceKey=linux}

{column}
{column:width=50%}

{recently-updated} 

{column}

{section}</property>
    

<property name="body">Sometimes, you have an ISO you've downloaded which you would like to access in linux, but don't want to go to the hassle of burning it.  The following command will allow you to mount it and read from it just like a CD:

mount -o loop _filename_.iso /mnt/_yourdirectory_

</property>
    

<property name="body">h2. First Step


h5. If IP is assigned by DHCP, make sure /etc/hosts file looks like this:
{code:title=/etc/hosts|borderStyle=solid}127.0.0.1     servername.suu.edu     localhost.localdomain     localhost     servername
{code}

h5. If IP is hard-coded, make sure /etc/hosts file looks like this (x.x is your new IP):
{code:title=/etc/hosts|borderStyle=solid}127.0.0.1     localhost.localdomain     localhost
134.250.x.x   yourserver.suu.edu        yourserver
{code}

h2. Second Step


h5. If you need the change to happen immediately without a reboot, run the following command as root:
{code:borderStyle=solid}#hostname yourserver.suu.edu
{code}

h2. Third Step


h5. This step is optional, and depends on the linux distribution and version you are using.  If you have an /etc/HOSTNAME file, ensure that it is populated with a single line as follows:
{code:borderStyle=solid}yourserver.suu.edu
{code}

h2. Fourth Step


h5. Edit the /etc/sysconfig/network file HOSTNAME line to read:
{code:title=/etc/sysconfig/network|borderStyle=solid}HOSTNAME=yourserver.suu.edu
{code}

h2. Fifth Step


h5. As root, run the following command:
{code:borderStyle=solid}#echo yourserver.suu.edu &gt; /proc/sys/kernel/hostname

To verify that it worked, run:
#cat /proc/sys/kernel/hostname
{code}

h2. Sixth Step


h5. Edit the /etc/sysconfig/network-scripts/ifcfg-eth0 file
{code}
DEVICE=eth0
BOOTPROTO=static (or dhcp)
ONBOOT=yes
HWADDR=[MAC Address]
NETMASK=255.255.255.0
IPADDR=[YOURIP]
GATEWAY=[YOURGW]
Type=Ethernet
{code}

h2. Finally, reboot.</property>
    

<property name="body">h1. Remove unnecessary services

{code:borderStyle=solid}
chkconfig --del anacron
chkconfig --del autofs
chkconfig --del apmd
chkconfig --del atd
chkconfig --del gpm
chkconfig --del irda
chkconfig --del isdn
chkconfig --del netfs
chkconfig --del nfs
chkconfig --del nfslock
chkconfig --del nscd
chkconfig --del ntpd
chkconfig --del portmap
chkconfig --del sendmail
chkconfig --del smartd
chkconfig --del snmpd
chkconfig --del snmptrapd
chkconfig --del winbind
chkconfig --del ypbind
chkconfig --del avahi-daemon
chkconfig --del cups
chkconfig --del exim
chkconfig --del firstboot
chkconfig --del gpm
chkconfig --del fuse
chkconfig --del mdmonitor  --handles software raid


cd /etc/xinetd.d/
rm -rf /etc/xinetd.d/chargen*
rm -rf /etc/xinetd.d/daytime*
rm -rf /etc/xinetd.d/echo*
rm -rf /etc/xinetd.d/rsync*
rm -rf /etc/xinetd.d/time*
{code}</property>
    

<property name="body">This document pertains to Redhat Enterprise Linux specifically, but may work for other distributions as well

h3. 1- Install VNC Server
#up2date vnc-server

h3. 2- Set it to start at boot
#chkconfig vncserver on

h3. 3- Set up servers for individual users
#vi /etc/sysconfig/vncservers
(insert the following lines into the file)
VNCSERVERS="1:usera 2:userb"   (add as many users as desired)
VNCSERVERARGS[1]="-geometry 1280x1024" (set resolution you desire for user a)
VNCSERVERARGS[2]="-geometry 1024x768" (set resolution you desire for user b)

h3. 4- Initialize VNC params for each user
#vncpasswd usera (enter password)
#vncpasswd userb (enter password)

h3. 5- Restart services
#/etc/init.d/vncserver restart

h3. 6- Edit each user's X startup script for VNC
#vi /home/usera/.vnc/xstartup
(the file should look like the following for full gui capability; for slow connections, there are much 'slimmer' options; this doc assumes local LAN connectivity)

h4. # The file should look like this for a normal desktop:
{code:title=/home/username/.vnc/xstartup|borderStyle=solid}
#!/bin/sh
# Uncomment the following two lines for normal desktop:
unset SESSION_MANAGER
exec /etc/X11/xinit/xinitrc


The file should look like this if you have a slow connection:

#!/bin/sh

# Uncomment the following two lines for normal desktop:
# unset SESSION_MANAGER
# exec /etc/X11/xinit/xinitrc

[ -x /etc/vnc/xstartup ] &amp;&amp; exec /etc/vnc/xstartup
[ -r $HOME/.Xresources ] &amp;&amp; xrdb $HOME/.Xresources
xsetroot -solid grey
vncconfig -iconic &amp;
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &amp;
twm &amp;
{code}

h3. 7- Restart services again
#/etc/init.d/vncserver restart

h3. 8- Connect with client from remote desktop
using the free RealVNC client, simply enter the following into the hostname prompt:
your.server.edu:1  (the :1 denotes user 'a' in this case; substitute other numbers accordingly)</property>
    

<property name="body">h3. Ubuntu
Sometimes when modifying the xorg.conf file, you'll mess it up and not have a backup.  Here's a command to restore the original as it was at install.

dpkg-reconfigure -phigh xserver-xorg</property>
    

<property name="body">h4. Current /etc/apt/mirror.list contents
{code}
############# config ##################
#
set base_path    /home/itftp/APTMIRROR
#
# if you change the base path you must create the directories below with write privileges
#
set mirror_path  $base_path/mirror
set skel_path    $base_path/skel
set var_path     $base_path/var
set cleanscript  $base_path/var/clean.sh
set defaultarch  i386
set nthreads     10
set _tilde 0
#
############# end config ##############
# Main packages for hardy, jaunty, lucid, maverick
deb-i386 http://archive.ubuntu.com/ubuntu hardy main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu hardy-updates main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu hardy main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu hardy-updates main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu jaunty main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu jaunty-updates main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu jaunty main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu jaunty-updates main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu lucid main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu lucid-updates main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu lucid main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu lucid-updates main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu maverick main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu maverick-updates main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu maverick main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu maverick-updates main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu natty main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu natty-updates main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu natty main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu natty-updates main restricted universe multiverse

# Updates for hardy, jaunty, lucid, maverick
deb-i386 http://archive.ubuntu.com/ubuntu hardy-security main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu hardy-security main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu jaunty-security main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu jaunty-security main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu lucid-security main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu lucid-security main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu maverick-security main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu maverick-security main restricted universe multiverse
deb-i386 http://archive.ubuntu.com/ubuntu natty-security main restricted universe multiverse
deb-amd64 http://archive.ubuntu.com/ubuntu natty-security main restricted universe multiverse
# Security updates
deb-i386 http://security.ubuntu.com/ubuntu hardy-security main restricted
deb-i386 http://security.ubuntu.com/ubuntu hardy-security universe
deb-i386 http://security.ubuntu.com/ubuntu hardy-security multiverse
deb-amd64 http://security.ubuntu.com/ubuntu hardy-security main restricted
deb-amd64 http://security.ubuntu.com/ubuntu hardy-security universe
deb-amd64 http://security.ubuntu.com/ubuntu hardy-security multiverse
deb-i386 http://security.ubuntu.com/ubuntu jaunty-security main restricted
deb-i386 http://security.ubuntu.com/ubuntu jaunty-security universe
deb-i386 http://security.ubuntu.com/ubuntu jaunty-security multiverse
deb-amd64 http://security.ubuntu.com/ubuntu jaunty-security main restricted
deb-amd64 http://security.ubuntu.com/ubuntu jaunty-security universe
deb-amd64 http://security.ubuntu.com/ubuntu jaunty-security multiverse
deb-i386 http://security.ubuntu.com/ubuntu lucid-security main restricted
deb-i386 http://security.ubuntu.com/ubuntu lucid-security universe
deb-i386 http://security.ubuntu.com/ubuntu lucid-security multiverse
deb-amd64 http://security.ubuntu.com/ubuntu lucid-security main restricted
deb-amd64 http://security.ubuntu.com/ubuntu lucid-security universe
deb-amd64 http://security.ubuntu.com/ubuntu lucid-security multiverse
deb-i386 http://security.ubuntu.com/ubuntu maverick-security main restricted
deb-i386 http://security.ubuntu.com/ubuntu maverick-security universe
deb-i386 http://security.ubuntu.com/ubuntu maverick-security multiverse
deb-amd64 http://security.ubuntu.com/ubuntu maverick-security main restricted
deb-amd64 http://security.ubuntu.com/ubuntu maverick-security universe
deb-amd64 http://security.ubuntu.com/ubuntu maverick-security multiverse
deb-i386 http://security.ubuntu.com/ubuntu natty-security main restricted
deb-i386 http://security.ubuntu.com/ubuntu natty-security universe
deb-i386 http://security.ubuntu.com/ubuntu natty-security multiverse
deb-amd64 http://security.ubuntu.com/ubuntu natty-security main restricted
deb-amd64 http://security.ubuntu.com/ubuntu natty-security universe
deb-amd64 http://security.ubuntu.com/ubuntu natty-security multiverse
# Partner repo
deb-i386 http://archive.canonical.com/ubuntu hardy partner
deb-amd64 http://archive.canonical.com/ubuntu hardy partner
deb-i386 http://archive.canonical.com/ubuntu jaunty partner
deb-amd64 http://archive.canonical.com/ubuntu jaunty partner
deb-i386 http://archive.canonical.com/ubuntu lucid partner
deb-amd64 http://archive.canonical.com/ubuntu lucid partner
deb-i386 http://archive.canonical.com/ubuntu maverick partner
deb-amd64 http://archive.canonical.com/ubuntu maverick partner
deb-i386 http://archive.canonical.com/ubuntu natty partner
deb-amd64 http://archive.canonical.com/ubuntu natty partner

# Extras (added as of Maverick)
deb-i386 http://extras.ubuntu.com/ubuntu maverick main
deb-amd64 http://extras.ubuntu.com/ubuntu maverick main
deb-i386 http://extras.ubuntu.com/ubuntu natty main
deb-amd64 http://extras.ubuntu.com/ubuntu natty main

# Cleanup scripts
clean http://archive.ubuntu.com
clean http://security.ubuntu.com
clean http://archive.canonical.com
{code}
h4. Current soft links in /var/www directory
{code}
root@sherpa:/var/www# ls -aslh
total 12K
4.0K drwxr-xr-x  2 root root 4.0K 2011-06-03 16:44 .
4.0K drwxr-xr-x 15 root root 4.0K 2011-06-02 16:58 ..
   0 lrwxrwxrwx  1 root root   53 2011-06-03 16:44 extras -&gt; /home/itftp/APTMIRROR/mirror/extras.ubuntu.com/ubuntu
4.0K -rw-r--r--  1 root root  177 2011-06-02 16:58 index.html
   0 lrwxrwxrwx  1 root root   54 2011-06-03 09:46 ubuntu -&gt; /home/itftp/APTMIRROR/mirror/archive.ubuntu.com/ubuntu
   0 lrwxrwxrwx  1 root root   57 2011-06-03 09:46 ubuntupartner -&gt; /home/itftp/APTMIRROR/mirror/archive.canonical.com/ubuntu
   0 lrwxrwxrwx  1 root root   55 2011-06-03 09:46 updates -&gt; /home/itftp/APTMIRROR/mirror/security.ubuntu.com/ubuntu
{code}
</property>
    

<property name="body">h3. Provided by Jeff Johnson:

No single tool, but here's what I do:

0) Make a copy of everything, just in case:
        cd /var/lib
        tar czvf /tmp/rpmdb.tar.gz rpm

1) Check /var/lib/rpm/Packages with db_verify.
        The command is
                db_verify /var/lib/rpm/Packages
        If that fails, the fix is
                cd /var/lib/rpm
                mv Packages Packages-ORIG
                db_dump Packages-ORIG | db_load Packages
        At this point Packages should be OK.

2) Read all Package headers.
        The command is
                rpm -qa
        If that "works", go to step 5), do "rpm --rebuilddb" and you're
done.
        If that segfaults, go to 3).
        if that hangs, then do
                rm -f /var/lib/rpm/__db*
        and try again.

3) You have a segfault on a header.
        The first step is to get the segfaulting header instance.
        Append "debug" to the Packages configuration by
          echo "%_dbi_config_Packages %{_dbi_htconfig} lockdbfd debug" \
                &gt;&gt; /etc/rpm/macros

        Try "rpm -qa", lots of boring glop until segfault.

        On the screen will be something like

    ...
    Get Packages key (0x8216580,4) data (0x4014f008,155244) "#612" 47000000
rc
0kernel-enterprise-2.4.9-26beta.17
    Get Packages key ((nil),0) data ((nil),0) "" deadbeef rc -30990
    &lt;segfault here&gt;

        The 2nd to last "Get Packages" line is what you want, the
        bad header instance above is "612" in decimal. Note the
        package name-version-release, you'll want to reinstall
        that package somewhen.

4) Nuke the bad header.
        I usually whip out my handy-dandy header instance deleter,
        edit the bad record into the source, compile, run, and go back
        to step 2).


        The program is at
                ftp://people.redhat.com/jbj/t38454.c
        FWIW, the program is named after the bugzilla report that
        caused me to write it.

        Retrieve, and edit the bad header instances into
                ...
  {code}              int badrecs[] = {
--&gt; EDIT --&gt;            562, 566, 559, 561, 563, 560, 564,
                        -1
                };
                ...

        Compile with
                cc -o t38454 t38454.c -ldb-3.2

        Run as
                t38454 {code}

        Go back to step 2).

5) Clean up.
        a) rpm --rebuilddb
        b) rm -f /etc/rpm/macros
        c) rm -rf /var/lib/rpmrebuild*
        d) Reinstall the deleted package.</property>
    

<property name="body">{suu-info}
This is the root page for our HAProxy documentation.
{suu-info}

{suu-tip}
*How to check on the status of things*
* *Check status of HAProxy*
** http://halb1.suu.edu:8001
** http://halb2.suu.edu:8001
** http://halb3.suu.edu:8001
* *Check the status of the nodes*
** SSH into one of the nodes
{code}
ssh halb1.suu.edu
sudo crm_mon --one-shot -V | grep Online
# The output will look something like this:
Online: [ halb1 halb2 halb3 ]
{code}

{suu-tip}


h2. Overview

* We have three load balancer nodes running in a cluster. They are active/active and will automatically take over for the other if one goes down.
* The load balance cluster has multiple shared IP addresses. The shared IP addresses are the user-facing IPs and that is where firewall rules are applied for user access.

Current production setup example: (note we have more stuff behind our load balancers, but this demonstrates the basic idea.)
{code}

        shared IP=12.141
            ^^^^^^^^
       12.142      12.143       5.24  5.25  
 -------+------------+-----------+-----+---
        |            |           |     |   
     +--+--+      +--+--+      +-+-+ +-+-+ 
     | LB1 |      | LB2 |      | A | | B | 
     +-----+      +-----+      +---+ +---+ 
     haproxy      haproxy       web servers
     heartbeat    heartbeat
     pacemaker    pacemaker

{code}
*LB1* = halb1.suu.edu
*LB2* = halb2.suu.edu
*A* = api1.suu.edu
*B* = api2.suu.edu
*shared IP* = api.suu.edu
</property>
    

<property name="body">{suu-info}
These are the steps you need to take to put a new service behind our HAProxy load balancers.
This document assumes that you already have your services running that you want to balance and that both load balancer nodes have appropriate firewall rules in place to access those services.
{suu-info}

h2. Setup HAProxy
{suu-info}
* You will need to modify the same file on both load balancer nodes.
* Both load balancer nodes need to have the appropriate firewall rules in place to get to your servers before this point.
* You should also know the front-facing ipaddress that your service will be using for this step.
{suu-info}
*Edit {{/etc/haproxy/haproxy.cfg}} (on both nodes)*

You will be adding a new server farm. Here is an example farm.

{code}
listen  api-webfarm 134.250.12.142:8000
        mode http
        balance roundrobin
        option httpclose
        option forwardfor
        option httpchk GET /banner
        server api1 134.250.5.24:8080 maxconn 1 check
        server api2 134.250.5.25:8080 maxconn 1 check
{code}
(!) The listen port must be unique, so if 8000 and 8001 are taken, use 8002

*Restart haproxy*
{code}
sudo /etc/init.d/haproxy restart
{code}

*Commit your changes*
{code}
cd /etc/haproxy/
sudo hg commit -m "New server config."
{code}

{suu-tip}
At this point, you should be able to see if HAProxy thinks your service is up or down by going to:
http://halb1.suu.edu:8001
http://halb2.suu.edu:8001
{suu-tip}

h2. Setup Apache
{suu-info}
* The same configuration will go on both load balander nodes, however, they are not exactly the same. IP addresses will be different.
* You can probably use an existing apache virtual host config file as a starting point. All you really need to do is then change ipaddresses and ports. No need to change the ssl settings because we are using our wildcard certificate.
{suu-info}

# Create a new virtual host configuration
{code}
sudo cp /etc/apache2/sites-available/api-ssl /etc/apache2/sites-available/yourservice-ssl
{code}
# Modify yourservice-ssl
{code}
sudo vim /etc/apache2/sites-available/yourservice-ssl
# Edit the ipaddress ie &lt;VirtualHost 134.250.12.141:443&gt; This should be the front-facing ipaddress for your application. The one that users will be connecting to.
# Edit just the ports in ProxyPass and ProxyPassReverse. The ports would be the haproxy ports you configured in the HAProxy step above.
{code}
# Enable your new virtual host
{code}
sudo a2ensite yourservice-ssl
{code}
# Reload apache
{code}
sudo /etc/init.d/apache2 reload
{code}
# Commit your changes
{code}
cd /etc/apache2/sites-available/
sudo hg add yourservice-ssl
sudo hg commit -m "New virtual host config file."
{code}
# Now do the same thing on the other load balancer node, but make sure the IP addresses for the *{{ProxyPass}}* and *{{ProxyPassReverse}}* are set to the IP address of that node.

h2. Setup your front-facing ipaddress
{suu-info}
* This step only needs to be done on one of the load balancer nodes. It will be automatically replicated to the second node.
* What you are doing here is setting up the ipaddress that users will hit. It is a shared ipaddress between the two nodes. This configuration is handled by Pacemaker
{suu-info}

{suu-tip}
*Tip:*
The following commands only need to be run on one node. They will be replicated automatically to the second node.
*api_ip* - is just the name we came up with to name this ip resource. This one is for the ip that will be used for api.suu.edu
*eth0" - the nic we want this ip to use.
{suu-tip}

# *Setup ipaddress resource*
{code}
sudo crm configure
crm(live)configure# primitive api_ip IPaddr params ip=134.250.12.141 cidr_netmask=255.255.255.0 nic=eth0
crm(live)configure# commit
crm(live)configure# exit
{code}
# *Set a preferred node for the ip resource*
This tells Pacemaker which node the resource ip should live on when both nodes are up.
{code}
sudo crm configure
crm(live)configure# location api_ip_pref api_ip 100: halb1
crm(live)configure# commit
crm(live)configure# exit
{code}
# *Setup Pacemaker monitoring*
{code}
sudo crm configure
crm(live)configure# monitor api_ip 40s:20s
crm(live)configure# commit
crm(live)configure# exit
{code}
# *Show running configuration*
{code}
sudo crm configure show
{code}

{suu-tip}
At this point, you should be able to hit your service on your front-facing ipaddress port 443 and get a response from your service.
{suu-tip}</property>
    

<property name="body">h2. Install Apache 

{code} 
sudo apt-get install apache2 libapache2-mod-proxy-html 
a2enmod ssl 
a2enmod proxy
a2enmod proxy_http
sudo service apache2 restart
{code} 

h2. Apache SSL 

Get our wildcard certificate and private key. 

{code} 
sudo mv server.crt /etc/ssl/certs/suu_edu.crt 
sudo mv server.key /etc/ssl/private/suu_edu.key 
{code} 

h2. Configure Apache Virtual Host 

{code} 
cd /etc/apache2/sites-available/ 
sudo cp default-ssl api-ssl 
sudo vim api-ssl 
# 
{code} 

h2. Install HAProxy 

# http://www.zivtech.com/blog/setting-ip-failover-heartbeat-and-pacemaker-ubuntu-lucid 

{code} 
sudo apt-get install haproxy 
{code} 

h2. Install heartbeat and pacemaker 

{code} 
sudo apt-get install heartbeat pacemaker 
{code} 

*Create ha.cf file (main heartbeat config file)* 
{code} 
sudo vim /etc/ha.d/ha.cf 
# Add the following 
autojoin none 
bcast eth0 
warntime 5 
deadtime 15 
initdead 60 
keepalive 2 
node halb1 
node halb2 
crm respawn 
{code} 

h2. Modify /etc/default/haproxy file
{code}
ENABLED=1
{code}
*Create authkeys file for heartbeat*  (original node only)
The following run as a shell script will generate the key, create the authkeys file and set proper permissions on the file. 
{code} 
#!/bin/bash 
( echo -ne "auth 1\n1 sha1 "; \ 
dd if=/dev/urandom bs=512 count=1 | openssl md5 ) \ 
&gt; /etc/ha.d/authkeys 
chmod 0600 /etc/ha.d/authkeys 
{code}
If this is an addtional node, simply copy the authkeys from the original server to your new node

*Restart heartbeat* 
{code} 
sudo /etc/init.d/heartbeat restart 
{code} 

*Verify that they are online* 
{code} 
sudo crm_mon -1 | grep Online 
{code} 

*Configure shared IPAddress* 
This is part of Pacemaker. To Pacemaker, an ipaddress is a resource. 

{suu-tip} 
*Tip:* 
The following commands only need to be run on one node. They will be replicated automatically to the second node. 
*api_ip* - is just the name we came up with to name this ip resource. This one is for the ip that will be used for api.suu.edu 
*eth0" - the nic we want this ip to use. 
{suu-tip} 

{code} 
sudo crm configure property stonith-enabled=false 
sudo crm configure 
crm(live)configure# primitive api_ip IPaddr params ip=134.250.12.141 cidr_netmask="255.255.255.0" nic="eth0" 
crm(live)configure# commit 
crm(live)configure# exit 
{code} 

*Set a preferred node for the ip resource* 
This tells Pacemaker which node the resource ip should live on when both nodes are up. 
{code} 
sudo crm configure 
crm(live)configure# location api_ip_pref api_ip 100: halb1 
crm(live)configure# commit 
crm(live)configure# exit 
{code} 

*Setup Pacemaker monitoring* 
{code} 
sudo crm configure 
crm(live)configure# monitor api_ip 15s:5s 
crm(live)configure# commit 
crm(live)configure# exit 
{code} 

*Show running configuration* 
{code} 
sudo crm configure show 
{code} </property>
    

<property name="body">{suu-info}
Documentation for managing a firewall on an Ubuntu box.
{suu-info}


h2. Overview

One of the simplest ways to manage a firewall on Ubuntu is to use the command *{{ufw}}*. It stands for "uncomplicated firewall" and it is installed by default. The firewall is not running by default though.

h2. Initial Setup

*Set default policy to deny*
{code}
sudo ufw default deny
{code}

*Turn on the firewall*
{code}
sudo ufw enable
{code}

h2. Some sample rules

*Allow a specific IP address on any port.*
{code}
sudo ufw allow from 134.250.4.188
{code}

*Allow a subnet range to a specific port*
{code}
# This allows ssh access from the VPN subnet.
sudo ufw allow from 134.250.236.0/24 to any port 22
{code}

*Block a specific IP*
{code}
sudo ufw deny 134.250.4.77
{code}</property>
    

<property name="body">{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client System Options file for UNIX (dsm.sys.smp)             *
************************************************************************

*  This file contains the minimum options required to get started
*  using TSM.  Copy dsm.sys.smp to dsm.sys.  In the dsm.sys file,
*  enter the appropriate values for each option listed below and
*  remove the leading asterisk (*) for each one.

*  If your client node communicates with multiple TSM servers, be
*  sure to add a stanza, beginning with the SERVERNAME option, for
*  each additional server.

************************************************************************

SErvername  tivoli
   COMMMethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu
nodename MARKETPLACE
passwordaccess generate
MANAGEDSERVICES	schedule webclient
include /home/.../*
include /etc/.../*
exclude.dir /bin
exclude.dir /boot
exclude.dir /dev
exclude.dir /initrd
exclude.dir /lib
exclude.dir /lost*
exclude.dir /media
exclude.dir /mnt
exclude.dir /opt
exclude.dir /proc
exclude.dir /root
exclude.dir /sbin
exclude.dir /srv
exclude.dir /tmp
exclude.dir /usr/bin
exclude.dir /usr/games
exclude.dir /usr/include
exclude.dir /usr/lib
exclude.dir /usr/sbin
exclude.dir /usr/share
exclude.dir /usr/src
exclude.dir /usr/X11R6
exclude.dir /usr/local/bin
exclude.dir /usr/local/games
exclude.dir /usr/local/include
exclude.dir /usr/local/lib
exclude.dir /usr/local/sbin
exclude.dir /usr/local/share
exclude.dir /usr/local/src
{code}</property>
    

<property name="body">{code}
SErvername  tivoli
   COMMmethod         TCPip
   TCPPort            1500
   TCPServeraddress   tivoli.suu.edu

nodename BIRCHINB 
passwordaccess generate
MANAGEDSERVICES	schedule webclient
include /u01/.../*
include /u02/.../*
include /u03/.../*
include /home/.../*
include /etc/.../*
include /root/.../*
exclude.dir /dev
exclude.dir /mnt
exclude.dir /opt
exclude.dir /proc
{code}</property>
    

<property name="body">1. Download the client zip file from sherpa or the Oracle site

2. Install the following additional packages:
{code}
#apt-get install libaio1 gawk
{code}
Additionally, be sure you are running the sun java software, not the default packaged version with Ubuntu.  You will also make a link for awk to gawk.
{code}
#apt-get install sun-java6-bin sun-java6-jre sun-java6-plugin sun-java6-jdk
#cd /etc/alternatives
#ln -s /usr/lib/jvm/java-6-sun/jre/bin/java java
#cd /usr/bin
#ln -s /usr/bin/gawk awk
{code}

3. Next, we will initiate the installer to see where it fails and what settings we need to add to our /etc/sysctl.conf file.  Initiate the installer as follows, and then CANCEL as soon as you have the values you need:
{code}
./runinstaller -ignoreSysPrereqs
{code}
You will reach a point where it checks for needed settings, and gives you a list of everything that does not meet requirements.  The settings you are interested in are listed in the next step.  Make a note of the values the installer recommends.

4. Add the following entries to your /etc/sysctl.conf file: (change values to match what is recommended for your machine - some will be the same, some won't)
{code}
# Oracle client stuff
kernel.shmmax = 536870912
kernel.sem = 250 32000 100 128
net.ipv4.ip_local_port_range = 9000 65500
net.core.rmem_default = 4194304
net.core.rmem_max = 4194304
net.core.wmem_default = 262144
net.core.wmem_max = 262144
{code}
Next, run the following to make the settings active:
{code}
#sysctl -p
{code}

5. Now you can run the installer and ignore the warnings completely (there is a checkbox to do this)
{code}
./runinstaller -ignoreSysPrereqs
{code}

6. Once it is finished, make a note of where you installed it to, and make the following entries in your .bashrc file:

{code}
#Oracle stuff
export ORACLE_HOME=/&lt;path_to_where_you_installed&gt;/product/11.2.0/client_1
export PATH=$PATH:$ORACLE_HOME/bin
export TNS_ADMIN=$ORACLE_HOME/network/admin
{code}
Next, run the following to make it active (NOT as root - run as your user):
{code}
$ . .bashrc
{code}
If that is difficult to read, it is:
{code}
&lt;dot&gt;&lt;space&gt;&lt;dot&gt;&lt;bashrc&gt;
{code}

7. Lastly, copy the contents of a known good tnsnames.ora file, and paste it into the following file:
{code}
$ORACLE_HOME/network/admin/tnsnames.ora
{code}

8. Run tnsping against any of the tnsnames entries, and make sure you get a response.</property>
    

<property name="body">1. Add the following line to the bottom of your /etc/apt/sources.list file:
{code}
deb http://download.virtualbox.org/virtualbox/debian] karmic non-free
{code}
2. Import the key:
{code}
sudo wget -q http://download.virtualbox.org/virtualbox/debian/sun_vbox.asc -O- | sudo apt-key add -
{code}

Refresh the repositories:
{code}
sudo apt-get update
{code}

3. Install the latest virtualbox package (as of this writing it is virtualbox-3.1) by selecting it in Synaptic, or running this command from a terminal:
{code}
 $ sudo apt-get install virtualbox-3.1
{code}
4.  Add yourself to the vboxusers group:
{code}
 $ sudo gpasswd -a YOURUSERNAME vboxusers
{code}
5.  Find the devgid for the vboxusers group:
{code}
 $ grep vboxusers /etc/group
{code}
It will return something like:
{code}
 vboxusers:x:121:username
{code}
Add this line to the bottom of /etc/fstab, replacing the devgid number with your devgid:
{code}
none /proc/bus/usb usbfs devgid=125,devmode=664 0 0
{code}

After you reboot you should now have USB support in VirtualBox.

Last tested on Ubuntu 9.10 Karmic Koala</property>
    

<property name="body">Similar to Windows Software Update Services, apt-mirror allows us to store a local copy of the Ubuntu updates repository so our machines don't all have to go out to the internet for updates. &amp;nbsp;Not only does this reduce our bandwidth usage, but updates are delivered extremely quickly over local wire. &amp;nbsp;Here is an example of an /etc/apt/sources.list file from an Ubuntu 10.04 LTS 32-bit server install, pointed at our local repository on sherpa.suu.edu:

{code}

deb http://sherpa.suu.edu/ubuntu/ lucid main restricted

## Major bug fix updates produced after the final release of the
## distribution.
deb http://sherpa.suu.edu/ubuntu/ lucid-updates main restricted

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://sherpa.suu.edu/ubuntu/ lucid universe
deb http://sherpa.suu.edu/ubuntu/ lucid-updates universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu 
## team, and may not be under a free licence. Please satisfy yourself as to 
## your rights to use the software. Also, please note that software in 
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://sherpa.suu.edu/ubuntu/ lucid multiverse
deb http://sherpa.suu.edu/ubuntu/ lucid-updates multiverse

## Uncomment the following line to add software from Canonical's
## 'partner' repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
## respective vendors as a service to Ubuntu users.
deb http://sherpa.suu.edu/ubuntupartner lucid partner

## Security Updates
deb http://sherpa.suu.edu/updates lucid-security main restricted
deb http://sherpa.suu.edu/updates lucid-security universe
deb http://sherpa.suu.edu/updates lucid-security multiverse

{code}

NOTE:  We do not currently mirror the deb-src (sources) files, since we rarely if ever compile our packages from source.  Adding these sources to every subsection listed here would more than double the required space to store them.  Your original sources.list file may or may not reference the source repositories.  If it does, you should remove the lines from your file, or at least comment them out.  If you need them, the only solution at this time is to leave them pointed at the original ubuntu location.


For reference, here is a standard unmodified sources.list from an 11.10 box:
{code}
deb http://us.archive.ubuntu.com/ubuntu/ oneiric main restricted
deb-src http://us.archive.ubuntu.com/ubuntu/ oneiric main restricted
deb http://us.archive.ubuntu.com/ubuntu/ oneiric-updates main restricted
deb-src http://us.archive.ubuntu.com/ubuntu/ oneiric-updates main restricted
deb http://us.archive.ubuntu.com/ubuntu/ oneiric universe
deb-src http://us.archive.ubuntu.com/ubuntu/ oneiric universe
deb http://us.archive.ubuntu.com/ubuntu/ oneiric-updates universe
deb-src http://us.archive.ubuntu.com/ubuntu/ oneiric-updates universe
deb http://us.archive.ubuntu.com/ubuntu/ oneiric multiverse
deb-src http://us.archive.ubuntu.com/ubuntu/ oneiric multiverse
deb http://us.archive.ubuntu.com/ubuntu/ oneiric-updates multiverse
deb-src http://us.archive.ubuntu.com/ubuntu/ oneiric-updates multiverse
# deb http://us.archive.ubuntu.com/ubuntu/ maverick-backports main restricted universe multiverse
# deb-src http://us.archive.ubuntu.com/ubuntu/ maverick-backports main restricted universe multiverse
deb http://archive.canonical.com/ubuntu oneiric partner
deb-src http://archive.canonical.com/ubuntu oneiric partner
deb http://extras.ubuntu.com/ubuntu oneiric main
deb-src http://extras.ubuntu.com/ubuntu oneiric main

deb http://security.ubuntu.com/ubuntu oneiric-security main restricted
deb-src http://security.ubuntu.com/ubuntu oneiric-security main restricted
deb http://security.ubuntu.com/ubuntu oneiric-security universe
deb-src http://security.ubuntu.com/ubuntu oneiric-security universe
deb http://security.ubuntu.com/ubuntu oneiric-security multiverse
deb-src http://security.ubuntu.com/ubuntu oneiric-security multiverse
{code}
</property>
    

<property name="body">{attachments:old=true}</property>
    

<property name="body">h1. Resizing Logical Volumes

This is a continuation of my earlier post. Here I will explain how to resize an existing logical volume. Logical volumes may be resized dynamically while preserving the data on the volume. Here is how:
# Reducing a logical volume.
# Reduce the filesystem residing on the logical volume.
# Reduce the logical volume.

For different file systems,it is achieved differently.

For ext2 filesystem
If you are using LVM 1, then both the above steps could be acomplished by executing a single utility called e2fsadm.
# umount /data
# e2fsadm \-L \-1G /dev/my_vol_grp/my_logical_vol
# mount /data
The above command first reduces the filesystem in the 'my_logical_vol'by 1 GB and then reduces themy_logical_vol itself by the same amount.
If you are using LVM 2 - more recent linux distributions like Fedora use LVM 2 - then you do not have the'e2fsadm' utility. So you have to first reduce the filesystem using 'resize2fs' and then reduce the logical volume using 'lvreduce'.
# umount /data
# resize2fs  /dev/my_vol_grp/my_logical_vol  1G
# lvreduce  \-L  1G  /dev/my_vol_grp/my_logical_vol
# mount /data
In the above case, I have reduced my file
# Grow a Logical Volume
The steps for growing a logical volume are the exact opposite of those for shrinking the logical volume.
# 
# Then resize the filesystem to the new size of your logical volume.</property>
    

<property name="body">h4. The latest client for Windows and Linux can be found on the Install volume (\\image1\install) in the \Tivoli\Linux or \Tivoli\Windows directory


h2. Example contents of dsm.opt file

{code}
************************************************************************
* IBM Tivoli Storage Manager                                           *
*                                                                      *
* Sample Client User Options file for UNIX (dsm.opt.smp)               *
************************************************************************

*  This file contains an option you can use to specify the TSM
*  server to contact if more than one is defined in your client
*  system options file (dsm.sys).  Copy dsm.opt.smp to dsm.opt.
*  If you enter a server name for the option below, remove the
*  leading asterisk (*).

************************************************************************

* SErvername       A server name defined in the dsm.sys file
SErvername	tivoli
{code}


h2. Configuring Automatic Startup
Create a file called suu_tivoli in the /etc/init.d directory, and place the following contents in it:

{code}
#!/bin/bash
# description: Starts the IBM Tivoli backup daemons
# chkconfig: 2345 99 00
export TIVBASE=/opt/tivoli/tsm/client/ba/bin;
export PATH=$PATH:$TIVBASE;
export DSM_DIR=$TIVBASE;
export DSM_CONFIG=$TIVBASE;
export DSM_LOG=$TIVBASE;
#export LANG=en_US;
#export LC_ALL=en_US;

case "$1" in
start)
        if [ -f "/var/lock/subsys/tivoli" ]; then
                printf "\nTivoli dsmcad has already been loaded\n\n"
                exit 2
        fi

        $TIVBASE/dsmcad
        ps -C dsmcad -o pid= &gt; /var/lock/subsys/tivoli
        ;;
stop)
        for i in `ps -C dsmcad -o pid=`; do
                kill $i
        done

        if [ -f "/var/lock/subsys/tivoli" ]; then
                rm -f /var/lock/subsys/tivoli
        fi
        ;;
*)
        echo "Usage: `basename $0` {start | stop}"
        exit 1
        ;;
esac

exit 0
{code}

h4. Next, execute the following commands:

{code}
FOR UBUNTU SERVER:

chmod 775 suu_tivoli
update-rc.d suu_tivoli defaults

FOR RED HAT:
chmod 755 suu_tivoli
chkconfig --add suu_tivoli
chkconfig --level 345 suu_tivoli on
{code}

h4. Finally, you must start the daemon manually and enter the password; this is only required once\- it will remember it going forward

At this point, it is assumed you have talked to Matt and set up a login and password for your server.  Run the following commands to initialize and run a backup:
{code}
#dsmc
It will prompt you for your nodename and password.  Once you have entered them, it will drop you at a tsm&gt; prompt.
You can then type 'backup', no quotes, and it will start an incremental backup.  If you don't want to start one right away,
just type 'quit', no quotes, and it will drop you back at the linux prompt.
To start the daemon, run the following command:

#/etc/init.d/suu_tivoli start
{code}

h2. Occasionally, the Tivoli upgrade process will break links to existing libraries; here's how to fix it.


h4. Error loading shared libraries

If you encounter the following message while starting dsmc
{code}
dsmc: error while loading shared libraries: libgpfs.so: cannot open shared object file: No such file or directory
{code}
you need to add the path to the dsm binary directory to the file _/etc/ld.so.conf_
{code}
/opt/tivoli/tsm/client/api/bin
/usr/local/ibm/gsk8/lib
{code}
&amp;nbsp;and then reimport the shared objects using the command
{code}
ldconfig
{code}

h4. English message repository not found

If you get the error message
{code}
ANS0101E Unable to open English message repository 'dsmclientV3.cat'.
{code}
you need to create a symbolic link in _/opt/tivoli/tsm/client/ba/bin_ with
{code}
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/en_US/
{code}

h2. Ubuntu Server Notes

{code}
Installing TSM Client V6.6.2 on Ubuntu 10.04 Server 64-bit



1) get the latest client - modify version numbers as needed
wget "ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v5r5/Linux/LinuxX86/v553/5.5.3.0-TIV-TSMBAC-LinuxX86.tar"

** NOTE - execute "sudo su -" prior to running the following build and install.  Otherwise, permissions get jacked

2) apt-get install alien ksh ia32-libs* libstdc++5 gawk
* only if installing on 64-bit host

3) unpack the archive
tar xvf 5.5.3.0-TIV-TSMBAC-LinuxX86.tar

4) unpack the RPM archives (ignore warnings re scripts)
alien -g TIVsm-API.i386.rpm
alien -g TIVsm-BA.i386.rpm

5) change directory names
mv TIVsm-API-5.5.3/debian TIVsm-API-5.5.3/DEBIAN
mv TIVsm-BA-5.5.3/debian TIVsm-BA-5.5.3/DEBIAN

6) edit the control files

vi TIVsm-API-5.5.3/DEBIAN/control
Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-api
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-api
Architecture: amd64
Depends:
Description: the API IBM Tivoli Storage Manager API
Version: 5.5.3
&lt;blank line&gt;

Save and exit the file.

vi TIVsm-BA-5.5.3/DEBIAN/control

Your edited file should look like the following: (be sure to leave one blank line at the end of the file)

Source: tivsm-ba
Section: alien
Priority: extra
Maintainer: Josh Foremaster &lt;foremaster@suu.edu&gt;
Package: tivsm-ba
Architecture: amd64
Depends:
Description: the Backup Archive Client IBM Tivoli Storage Manager Client
Version: 5.5.3
&lt;blank line&gt;

Save and exit the file

7) create *.deb packages
dpkg -b TIVsm-API-5.5.3
dpkg -b TIVsm-BA-5.5.3

8) install *.deb packages
dpkg -i TIVsm-API-5.5.3.deb
dpkg -i TIVsm-BA-5.5.3.deb

9) mkdir -p /var/lock/subsys
   touch /var/lock/subsys/tivoli

10) create/modify TSM configuration files
 (use examples listed above)
vi /opt/tivoli/tsm/client/ba/bin/dsm.opt
vi /opt/tivoli/tsm/client/ba/bin/dsm.sys


12) Link the necessary shared libraries:
add the dsm binary path on a line in the file /etc/ld.so.conf
/opt/tivoli/tsm/client/api/bin
import the shared objects using the command
ldconfig
cd /opt/tivoli/tsm/client/ba/bin
ln -s ../../lang/EN_US/

13) run an incremental backup
dsmc incremental

14) start the TSM scheduler
#/etc/init.d/suu_tivoli start
{code}</property>
    

<property name="body">h3. Create a file called suu_startup in the /etc/init.d directory.  Be sure to replace &lt;server&gt; with your server's name, i.e. oak, aspen, etc. Save file and proceed to next steps.

{code}
#!/bin/bash
#
# chkconfig: 35 98 01
# description: Starts Oracle Application Server software
#

export SOURCE=/u01/app/oracle/scripts
export USER=root
touch /var/lock/subsys/suu_startup
case "$1" in
start)
        echo -n "Starting suu_startup"

        if [ -f "$SOURCE/start&lt;server&gt;.ksh" ]; then
                $SOURCE/start&lt;server&gt;.ksh #&gt; /tmp/start&lt;server&gt;.log 2&gt;&amp;1
        fi
        ;;
stop)
        echo -n "Stopping suu_startup"

        if [ -f "$SOURCE/stop&lt;server&gt;.ksh" ]; then
                $SOURCE/stop&lt;server&gt;.ksh #&gt; /tmp/stop&lt;server&gt;.log 2&gt;&amp;1
        fi
        ;;
*)
        printf "Usage: `basename $0` {start | stop}\n"
        exit 1
        ;;
esac

exit 0
{code}

h4. Step 2 - chmod 755 suu_startup
h4. Step 3 - chkconfig --add suu_startup
h4. Step 4 - chkconfig --level 345 suu_startup on</property>
    

<property name="body">CUPS Doc
To install cups and hplip on a new server, here is the procedure:

CUPS:
1\- ensure you have the following packages installed:
gcc, libjpeg, libjpeg-devel, libpng, libpng-devel, libtiff, libtiff-devel, zlib, zlib-devel,dbus-devel,php-devel,pyqt,pyqt-devel,xsane,net-snmp-devel

2\- Download the latest stable source from www.cups.org (1.3.6 as of this writing)

3\- Compile the source as follows:
{code}
rpmbuild -ta cups-version-source.tar.gz --without dbus
{code}
This will produce several compiled rpms in the /usr/src/redhat/RPMS/i386 directory.
The only ones you want are cups, cups-libs, cups-debuginfo, cups-devel,cups-lpd,cups-php
Do an rpm \-Uvh on all these packages.

HPLIP:
{code}
#tar -zxvf hplip-****.gz
#cd hplip-****
#(as banjobs, not ROOT) ./configure --enable-network-build --disable-dbus-build --disable-pp-build --disable-fax-build --disable-gui-build --disable-scan-build --enable-doc-build --enable-foomatic-ppd-install --disable-foomatic-drv-install --with-hpppddir=/usr/share/cups/model/HP --disable-hpijs-only-build --prefix=/usr
#(as banjobs, not ROOT) make
#(as ROOT) make install
#/etc/init.d/hplip restart
{code}
The following command creates a print queue called tranb on Solaris
lpadmin \-p tranb \-v/dev/null \-m netstandard \-o dest=134.250.51.248:3002 \-T PS \-I postscript \-o protocol=tcp

\--landscape using LPR

lpr  \-o landscape \-o cpi=15 \-o lpi=12 \-o cpi=16 \-Pormond SHRTRTC_876.lis

Cups Options:

Jobs can also have options associated with them such as media size, number of copies, and priority.
CUPS supports collections of printers known as classes. Jobs sent to a class are forwarded to the first available printer in the class.
Filters allow a user or application to print many types of files without extra effort. Print jobs sent to a CUPS server are filtered before sending them to a printer.
Some filters convert job files to different formats that the printer can understand. Others perform page selection and ordering tasks.

CUPS provides filters for printing many types of image files, HP-GL/2 files, PDF files, and text files.
CUPS also supplies PostScript and image file Raster Image Processor ("RIP") filters that convert PostScript or image files into bitmaps that can be sent to a raster printer.

CUPS also provides implicit classes, which are collections of printers and/or classes with the same name. This allows you to setup multiple servers pointing to the same physical network printer,
for example, so that you aren't relying on a single system for printing.  Because this also works with printer classes, you can setup multiple servers and printers
and never worry about a single point of failure unless all of the printers and servers go down\!

General Options

The following options apply when printing all types of files.
Selecting the Media Size, Type, and Source

The \-o media=xyz option sets the media size, type, and/or source:

lp \-o media=Letter filename ENTER
lp \-o media=Letter,MultiPurpose filename ENTER
lpr \-o media=Letter,Transparency filename ENTER
lpr \-o media=Letter,MultiPurpose,Transparency filename ENTER

The available media sizes, types, and sources depend on the printer, but most support the following options (case is not significant):
* Letter - US Letter (8.5x11 inches, or 216x279mm)
* Legal - US Legal (8.5x14 inches, or 216x356mm)
* A4 - ISO A4 (8.27x11.69 inches, or 210x297mm)
* COM10 - US #10 Envelope (9.5x4.125 inches, or 241x105mm)
* DL - ISO DL Envelope (8.66x4.33 inches, or 220x110mm)
* Transparency - Transparency media type or source
* Upper - Upper paper tray
* Lower - Lower paper tray
* MultiPurpose - Multi-purpose paper tray
* LargeCapacity - Large capacity paper tray

The actual options supported are defined in the printer's PPD file in the PageSize, InputSlot, and MediaType options.
Setting the Orientation

The \-o landscape option will rotate the page 90 degrees to print in landscape orientation:

lp \-o landscape filename ENTER
lpr \-o landscape filename ENTER

Printing On Both Sides of the Paper

The \-o sides=two-sided-short-edge and \-o sides=two-sided-long-edge options will enable duplexing on the printer, if the printer supports it. The \-o sides=two-sided-short-edge option is suitable for landscape pages, while the \-o sides=two-sided-long-edge option is suitable for portrait pages:

lp \-o sides=two-sided-short-edge filename ENTER
lp \-o sides=two-sided-long-edge filename ENTER
lpr \-o sides=two-sided-long-edge filename ENTER

The default is to print single-sided:

lp \-o sides=one-sided filename ENTER
lpr \-o sides=one-sided filename ENTER

Banner Options

The following options apply when printing all types of files.
Selecting the Banner Page(s)

The \-o jobsheets=start,end option sets the banner page(s) to use for a job:

lp \-o job-sheets=none filename ENTER
lp \-o job-sheets=standard filename ENTER
lpr \-o job-sheets=classified,classified filename ENTER

If only one banner file is specified, it will be printed before the files in the job. If a second banner file is specified, it is printed after the files in the job.

The available banner pages depend on the local system configuration; CUPS includes the following banner files:
* none - Do not produce a banner page.
* classified - A banner page with a "classified" label at the top and bottom.
* confidential - A banner page with a "confidential" label at the top and bottom.
* secret - A banner page with a "secret" label at the top and bottom.
* standard - A banner page with no label at the top and bottom.
* topsecret - A banner page with a "top secret" label at the top and bottom.
* unclassified - A banner page with an "unclassified" label at the top and bottom.

Document Options

The following options apply when printing all types of files.
Selecting a Range of Pages

The \-o page-ranges=pages option selects a range of pages for printing:

lp \-o page-ranges=1 filename ENTER
lp \-o page-ranges=1-4 filename ENTER
lp \-o page-ranges=1-4,7,9-12 filename ENTER
lpr \-o page-ranges=1-4,7,9-12 filename ENTER

As shown above, the pages value can be a single page, a range of pages, or a collection of page numbers and ranges separated by commas. The pages will always be printed in ascending order, regardless of the order of the pages in the page-ranges option.

The default is to print all pages.
Selecting Even or Odd Pages

Use the \-o page-set=set option to select the even or odd pages:

lp \-o page-set=odd filename ENTER
lp \-o page-set=even filename ENTER
lpr \-o page-set=even filename ENTER

The default is to print all pages.
Setting the Output Order

The the \-o outputorder=order option to set the output order of all pages:

lp \-o outputorder=normal filename ENTER
lp \-o outputorder=reverse filename ENTER
lpr \-o outputorder=reverse filename ENTER

N-Up Printing

The \-o number-up=value option selects N-Up printing. N-Up printing places multiple document pages on a single printed page. CUPS supports 1, 2, 4, 6, 9, and 16-Up formats; the default format is 1-Up:

lp \-o number-up=1 filename ENTER
lp \-o number-up=2 filename ENTER
lp \-o number-up=4 filename ENTER
lpr \-o number-up=16 filename ENTER

The \-o page-border=value option chooses the border to draw around each page:
* \-o page-border=double; draw two hairline borders around each page
* \-o page-border=double-thick; draw two 1pt borders around each page
* \-o page-border=none; do not draw a border (default)
* \-o page-border=single; draw one hairline border around each page
* \-o page-border=single-thick; draw one 1pt border around each page

The \-o number-up-layout=value option chooses the layout of the pages on each output page:
* \-o number-up-layout=btlr; Bottom to top, left to right
* \-o number-up-layout=btrl; Bottom to top, right to left
* \-o number-up-layout=lrbt; Left to right, bottom to top
* \-o number-up-layout=lrtb; Left to right, top to bottom (default)
* \-o number-up-layout=rlbt; Right to left, bottom to top
* \-o number-up-layout=rltb; Right to left, top to bottom
* \-o number-up-layout=tblr; Top to bottom, left to right
* \-o number-up-layout=tbrl; Top to bottom, right to left

Mirroring Prints

You can mirror a print using the \-o mirror option:

lp \-o mirror filename ENTER
lpr \-o mirror filename ENTER

This is useful for printing mirrored pages on transfer paper, for T shirts, mugs, etc.
Setting the Brightness

You can control the overall brightness of the printed output using the \-o brightness=percent option:

lp \-o brightness=120 filename ENTER
lpr \-o brightness=120 filename ENTER

Values greater than 100 will lighten the print, while values less than 100 will darken it.
Setting the Gamma Correction

You can control the overall gamma correction of the printed output using the \-o gamma=value option:

lp \-o gamma=1700 filename ENTER
lpr \-o gamma=1700 filename ENTER

Values greater than 1000 will lighten the print, while values less than 1000 will darken it. The default gamma is 1000.
Text Options

The following options apply when printing text files.
Setting the Number of Characters Per Inch

The \-o cpi=value option sets the number of characters per inch:

lp \-o cpi=10 filename ENTER
lp \-o cpi=12 filename ENTER
lpr \-o cpi=17 filename ENTER

The default characters per inch is 10.
Setting the Number of Lines Per Inch

The \-o lpi=value option sets the number of lines per inch:

lp \-o lpi=6 filename ENTER
lpr \-o lpi=8 filename ENTER

The default lines per inch is 6.
Setting the Number of Columns

The \-o columns=value option sets the number of text columns:

lp \-o columns=2 filename ENTER
lpr \-o columns=3 filename ENTER

The default number of columns is 1.
Setting the Page Margins

Normally the page margins are set to the hard limits of the printer. Use the \-o page-left=value, \-o page-right=value , \-o page-top=value, and \-o page-bottom=value options to adjust the page margins:

lp \-o page-left=value filename ENTER
lp \-o page-right=value filename ENTER
lp \-o page-top=value filename ENTER
lp \-o page-bottom=value filename ENTER
lpr \-o page-bottom=value filename ENTER

The value argument is the margin in points; each point is 1/72 inch or 0.35mm.
Pretty Printing

The \-o prettyprint option puts a header at the top of each page with the page number, job title (usually the filename), and the date. Also, C and C+\+ keywords are highlighted, and comment lines are italicized:

lp \-o prettyprint filename ENTER
lpr \-o prettyprint filename ENTER

Image Options

The following options apply when printing image files.
Positioning the Image

The \-o position=name option specifies the position of the image on the page:
* center - Center the image on the page (default)
* top - Print the image centered at the top of the page
* left - Print the image centered on the left of page
* right - Print the image centered on the right of the page
* top-left - Print the image at the top left corner of the page
* top-right - Print the image at the top right corner of the page
* bottom - Print the image centered at the bottom of the page
* bottom-left - Print the image at the bottom left corner of the page
* bottom-right - Print the image at the bottom right corner of the page

Scaling the Image

The \-o scaling=percent, \-o ppi=value, and \-o natural-scaling=percent options change the size of a printed image:

lp \-o scaling=percent filename ENTER
lp \-o ppi=value filename ENTER
lpr \-o natural-scaling=percent filename ENTER

The scaling=percent value is a number from 1 to 800 specifying the size in relation to the page (not the image.) A scaling of 100 percent will fill the page as completely as the image aspect ratio allows. A scaling of 200 percent will print on up to 4 pages.

The ppi=value value is a number from 1 to 1200 specifying the resolution of the image in pixels per inch. An image that is 3000x2400 pixels will print 10x8 inches at 300 pixels per inch, for example. If the specified resolution makes the image larger than the page, multiple pages will be printed to satisfy the request.

The natural-scaling=percent value is a number from 1 to 800 specifying the size in relation to the natural image size. A scaling of 100 percent will print the image at its natural size, while a scaling of 50 percent will print the image at half its natural size. If the specified scaling makes the image larger than the page, multiple pages will be printed to satisfy the request.
Adjusting the Hue (Tint) of an Image

The \-o hue=value option will adjust the hue of the printed image, much like the tint control on your television:

lp \-o hue=value filename ENTER
lpr \-o hue=value filename ENTER

The value argument is a number from \-360 to 360 and represents the color hue rotation. The following table summarizes the change you'll see with different colors:
Original	hue=-45	hue=45
Red	Purple	Yellow-orange
Green	Yellow-green	Blue-green
Yellow	Orange	Green-yellow
Blue	Sky-blue	Purple
Magenta	Indigo	Crimson
Cyan	Blue-green	Light-navy-blue

The default hue adjustment is 0.
Adjusting the Saturation (Color) of an Image

The \-o saturation=percent option adjusts the saturation of the colors in an image, much like the color knob on your television:

lp \-o saturation=percent filename ENTER
lpr \-o saturation=percent filename ENTER

The percent argument specifies the color saturation from 0 to 200. A color saturation of 0 produces a black-and-white print, while a value of 200 will make the colors extremely intense.

The default saturation is 100.
HP-GL/2 Options

The following options apply to HP-GL/2 files.
Printing in Black

The \-o blackplot option specifies that all pens should plot in black:

lp \-o blackplot filename ENTER
lpr \-o blackplot filename ENTER

The default is to use the colors defined in the plot file or the standard pen colors defined in the HP-GL/2 reference manual from Hewlett Packard.
Fitting the Plot on the Page

The \-o fitplot option specifies that the plot should be scaled to fit on the page:

lp \-o fitplot filename ENTER
lpr \-o fitplot filename ENTER

The default is to use the absolute distances specified in the plot file.
NOTE:

This feature depends upon an accurate plot size (PS) command in the HP-GL/2 file. If no plot size is given in the file than the HP-GL/2 filter assumes the plot is ANSI E size.

Setting the Default Pen Width

The \-o penwidth=value option specifies the default pen width for HP-GL/2 files:

lp \-o penwidth=value filename ENTER
lpr \-o penwidth=value filename ENTER

The pen width value specifies the pen width in micrometers. The default value of 1000 produces lines that are 1 millimeter in width. Specifying a pen width of 0 produces lines that are exactly 1 pixel wide.
NOTE:

This option is ignored when the pen widths are set in the plot file.

Raw or Unfiltered Output

The \-o raw option allows you to send files directly to a printer without filtering. This is sometimes required when printing from applications that provide their own "printer drivers" for your printer:

lp \-o raw filename ENTER
lpr \-o raw filename ENTER

The \-l option can also be used with the lpr command to send files directly to a printer:

lpr \-l filename ENTER

4 - Saving Printer Options and Defaults

This chapter describes how to save printer options for your printer and set your own default printer.
Printer Options

Each printer supports a large number of options, which you learned about in Chapter 3, "Standard Printer Options". Rather than specifying these options each time you print a file, CUPS allows you to save them as "default" options for the printer.

The lpoptions(1) command saves the options for your printers. Like the lp and lpr commands, it accepts printer options using the \-o argument:

lpoptions \-o prettyprint ENTER
lpoptions \-o media=A4 \-o sides=two-sided-long-edge ENTER
lpoptions \-o media=Legal \-o scaling=100 ENTER

Once saved, any lp or lpr command will use them when you print.
Note:

Running the lpoptions command as the root user (or any user with a UID of 0) will set the default options for all users. The root account does not have its own set of default options.

Setting Options for a Specific Printer

The previous example shows how to set the options for the default printer. The \-p printer option specifies the options are for another printer:

lpoptions \-p laserjet \-o prettyprint ENTER
lpoptions \-p laserjet \-o media=A4 \-o sides=two-sided-long-edge ENTER
lpoptions \-p deskjet \-o media=Legal \-o scaling=100 ENTER

Removing Options

The previous two examples shows how to set options for the default and a specific printer. Below, shows you how to remove the saved option using the \-r argument:

lpoptions \-r prettyprint ENTER
lpoptions \-p laserjet \-r prettyprint ENTER

Viewing the Current Defaults

The lpoptions command can also be used to show the current options by not specifying any new options on the command-line:

lpoptions ENTER
media=A4 sides=two-sided-long-edge
lpoptions \-p deskjet ENTER
media=Legal scaling=100

Viewing Options for a Specific Printer

You can display the supported options using the lpoptions command with the \-l option, as follows:

lpoptions \-p laserjet \-l ENTER

Setting the Default Printer

The administrator normally will set a system-wide default printer that is normally used as the default printer by everyone. Use the \-d printer option to set your own default printer:

lpoptions \-d deskjet ENTER

The printer can be local (deskjet) or remote ( deskjet@server).
Printer Instances

Besides setting options for each print queue, CUPS supports printer instances which allow you to define several different sets of options for each printer. You specify a printer instance using the slash (/) character:

lpoptions \-p laserjet/duplex \-o sides=two-sided-long-edge ENTER
lpoptions \-p laserjet/legal \-o media=Legal ENTER

The lp and lpr commands also understand this notation:

lp \-d laserjet/duplex filename ENTER
lpr \-P laserjet/legal filename ENTER

Removing Instances

Use the \-x printer/instance option to remove a printer instance that you no longer need:

lpoptions \-x laserjet ENTER
lpoptions \-x laserjet/duplex ENTER
lpoptions \-x laserjet/legal ENTER

The \-x option only removes the default options for that printer and instance; the original print queue will remain until deleted with the lpadmin(8) command by the administrator.
# Allow printing to printer MyLaserJet from
# itself and computers 192.10.2.5 and 192.10.2.6
&lt;Location /printers/MyLaserJet&gt;
...
Order deny,allow
Deny from all
Allow from 127.0.0.1
Allow from 192.10.2.5
Allow from 192.10.2.6
&lt;/Location&gt;

# Allow printing to printer MyLaserJet from
# itself and all computers on subnet 192.10.2.x
&lt;Location /printers/MyLaserJet&gt;
...
Order deny,allow
Deny from all
Allow from 127.0.0.1
Allow from 192.10.2.0/255.255.255.0
&lt;/Location&gt;</property>
    

<property name="body">h3. Bash Template for Oracle/Crystal server on Linux:
{code}
# .bash_profile

# Get the aliases and functions
if [ -f ~/.bashrc ]; then
	. ~/.bashrc
fi
CRYSTALDIR=/usr/local/CE10/crystal; export CRYSTALDIR
# User specific environment and startup programs
TOM=/usr/jakarta-tomcat-5.0.28; export TOM
JAVA_HOME=/usr/java/j2sdk1.4.2_05; export JAVA_HOME
CATALINA_HOME=/usr/jakarta-tomcat-5.0.28; export CATALINA_HOME
TWO_TASK=DEV; export TWO_TASK
LD_ASSUME_KERNEL=2.4.1; export LD_ASSUME_KERNEL
ORACLE_BASE=/opt/oracle; export ORACLE_BASE
ORACLE_HOME=/opt/oracle/product/9.2.0; export ORACLE_HOME
ORACLE_SID=DEV; export ORACLE_SID
ORACLE_OWNER=oracle; export ORACLE_OWNER
SH_LIB_PATH=$ORACLE_HOME/lib; export SH_LIB_PATH
TNS_ADMIN=$ORACLE_HOME/network/admin; export TNS_ADMIN
ORACLE_TERM=xterm; export ORACLE_TERM
CLASSPATH=/opt/oracle/product/9.2.0/jdbc/lib/classes111.zip:/usr/local/CE10/crystal/enterprise/java/applications/cewcanative.jar; export CLASSPATH
NLS_LANG=AMERICAN; export NLS_LANG
ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data; export ORA_NLS33
LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib; export LD_LIBRARY_PATH
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib; export LD_LIBRARY_PATH
PATH=$PATH:$ORACLE_HOME/bin:$HOME/bin:/usr/java/j2sdk1.4.2_05/bin
#BASEDIR=$TOM; export BASEDIR
export PATH
unset USERNAME
{code}</property>
    

<property name="body">h2. This document assumes you have the ncpmount, ncp, ncplogin, ncpmap, and ncpumount utilities installed on your machine
{code}
ncpmount -S cl01-adusers-server -A 134.250.12.107 -U username.it.administration.suu -V adusers/IT/Yourdir /dir/where/youwantitmountedonlocalfilesystem
{code}</property>
    

<property name="body">SQUID INSTALLATION:
Sent subscribe request to squid-users-subscribe@squid-cache.org

#Fix open files limit - added the following to /etc/security/limits.conf

squid soft nofile 4096
squid hard nofile 63536

#Added the following line to /usr/include/bits/types.h file:
#define _ _FD_SETSIZE    8192

#Ran the following as root; these will need to be executed before squid start; we will
stick them in the rc.d script:
ulimit -Hn 8192
echo "1024 61000" &gt; /proc/sys/net/ipv4/ip_local_port_range

Configure command:
./configure --prefix=/usr/local/squid --localstatedir=/squidcache/var --sysconfdir=/etc --enable-useragent-log --enable-icmp --enable-delay-pools --enable-htcp
 --enable-referer-log --enable-snmp --enable-cachemgr-hostname=squidcache.suu.edu --enable-ssl --with-openssl=/usr/local/ssl --enable-cache-digests --disable-http-violations

</property>
    

<property name="body">{code}The key to creating self-signed certificates in Tomcat is to remember the key files/components involved:
&lt;yourkeystore&gt; and cacerts, and an existing Java HOME variable.


&lt;yourkeystore&gt; will be whatever you decide to call it when creating the self-signed certificate.  For example, the following
command creates a keystore called mykeystore with an alias of tomcat and a validity of 10 years in the C:\ssl directory:

%JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA -keystore C:\ssl\mykeystore -validity 3650
remember first and last name must be the host+domain, i.e. tntrans.suu.edu

Export it:
%JAVA_HOME%\bin\keytool -export -alias tomcat -file D:\ssl\exported.cert -keystore C:\ssl\mykeystore

Once created, then you must import it into your existing CACERTS file for it to be 'trusted':

%JAVA_HOME%\bin\keytool -import -alias tomcat -trustcacerts -file D:\SSL\exported.cert -keystore %JAVA_HOME%\jre\lib\security\cacerts (this pass will be changeit)
{code}{color:#333333}Installing your Certificate with Jakarta-Tomcat.{color}
{color:#333333}(For Linux &amp; Windows){color}{color:#333333}&amp;nbsp;{color}
| {color:#333333}This document explains how to generate and install a Server Digital Certificate, and answers any question you might have.{color} || {color:#333333}{*}Creating a Certificate Signing Request{*}{color}\\ |
| {color:#333333}1. Generate a private key with the following command:{color}\\  {color:#333333}*$JAVA_HOME/bin/keytool \-genkey \-alias tomcat \-keyalg RSA \-keysize 1024 \-validity 730 \-keystore /path/to/domainname.kdb{*}{color}\\  \\ {color:#333333}You will be prompted for a password. Tomcat uses a default password of "changeit" - do NOT use that. If you use a different password, you will need to specify a custom password in the server.xml configuration file.{color}\\  \\ {color:#333333}In the next field you will be asked "What is your first and last name?" At this prompt, you must specify the common name (FQDN) of your web site.{color}\\  {color:#333333}You will then be prompted for your organizational unit, organization, etc.{color}\\  \\ {color:#333333}2. Generate the Certificate Signing Request (CSR){color}\\  {color:#333333}*$JAVA_HOME/bin/keytool \-certreq \-alias tomcat \-keystore /path/to/keystore.kdb \-file servername.csr{*}{color}\\  \\  {color:#333333}3. Now go to{color}{color:#333333}&amp;nbsp;{color}ipsCA{color:#333333}&amp;nbsp;{color}{color:#333333}, select your certificate and fill in the form with your personal data, paste your certificate request in the CSR field and make sure that you include BEGIN NEW CERTIFICATE REQUEST and END NEW CERTIFICATE REQUEST in your copied text.{color}\\
\\  {color:#333333}4. Make a backup of the keystore.kdb key database. It would be useful for you if your server crashes.{color}\\ | |
| {color:#333333}{*}Installing a Server Digital Certificate{*}{color}\\ |
| {color:#333333}{*}Upload a New SSL Certificate{*}{color}\\  {color:#333333}After you receive your certificate,{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}two other certificates will be necessary to setup your SSL Server, IPS SERVIDORES ROOT CERTIFICATE and the intermediate CA IPSCA CLASEA1{*}{color}{color:#333333}.{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}It is essential that these certificates are also&amp;nbsp; installed on your webserver in order to establish correct SSL connections{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}with your customer's browsers. Should they be required, you may download these certificates individually or collectively as a bundled file below:{color}\\
IPSServidores.crt \\
IPSCACLASEA1.crt \\
IPS-IPSCABUNDLE.CRT \\  {color:#333333}You must first export the certificates in the following format:{color}
# {color:#333333}Copy the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{_}IPSCACLASEA1 Chained CA certificate{_}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}into a text editor such as notepad and save as{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{_}chain.cer{_}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}on a Windows machine with IE 5+.{color}
# {color:#333333}Copy your{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{_}web server certificate{_}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}into a text editor such as notepad and save as{color}{color:#333333}{_}yourdomain.cer{_}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}on a Windows machine with IE 5+.{color}
# {color:#333333}Copy the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{_}IPSServidores root CA{_}{color}{color:#333333}_&amp;nbsp;_{color}{color:#333333}{_}certificate{_}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}into a text editor and save as{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{_}root.cer{_}{color}{color:#333333}_&amp;nbsp;_{color}{color:#333333}on a Windows machine with IE 5+.{color}
# {color:#333333}Double-click the root.cer and select the Details tab, then Copy to File, then select the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}Base-64{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}option, give your copied certificate a file name of{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}root_der.cer{*}{color}
# {color:#333333}Double-click the chain.cer and select Install. Choose "Place all certificates in following store" and select Intermediate Certification Authorities. Complete the Wizard.{color}
# {color:#333333}Double-click the chain.cer again and select the Details tab, then Copy to File, then select the{color}{color:#333333}{*}Base-64{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}option, give your copied certificate a file name of{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}chain_der.cer{*}{color}
# {color:#333333}Double click the youdomain.cer and select the Details tab, then Copy to File, then select the{color}{color:#333333}{*}PKCS#7 (p7b)*{color}{color:#333333}&amp;nbsp;{color}{color:#333333}option, also select the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}Include all certificates in the certification path{*}{color}{color:#333333}, give your copied certificate a file name of{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}yourdomain.p7b{*}{color}{color:#333333}{*}The following certificate installations must be executed in the stated order.*{color}\\  {color:#333333}1. Import the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}root_der.cer{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}and{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}chain_der.cer{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}files using:{color}{color:#333333}*$ keytool \-import \-trustcacerts \-keystore my.kdb \-alias root - file root_der.cer{*}{color}\\  {color:#333333}*$ keytool \-import \-trustcacerts \-keystore my.kdb \-alias chain - file chain_der.cer{*}{color}{color:#333333}{*}{color}{color:#333333}With my.kdb being your keystore.{color}\\  {color:#333333}2. Import the{color}{color:#333333}&amp;nbsp;{color}{color:#333333}{*}yourdomain.p7b file{*}{color}{color:#333333}&amp;nbsp;{color}{color:#333333}using:{color}{color:#333333}{*}{color}{color:#333333}{*}keytool \-import \-trustcacerts \-keystore my.kdb \-alias tomcat \-file yourdomain.p7b{*}{color}{color:#333333}{*}{color}{color:#333333}With my.kdb being your keystore.{color}\\  {color:#333333}&amp;nbsp;{color}\\  {color:#333333}{*}Update server.xml configuration{color} {color:#333333}[file:\*|file:*]{color}\\  {color:#333333}1. Open "$JAKARTA_HOME/conf/server.xml" in a text editor.{color}\\  {color:#333333}2. Find the following section:{color}\\  {color:#333333}&lt;Connector{color}{color:#333333}&amp;nbsp;{color}\\  {color:#333333}...{color}{color:#333333}&amp;nbsp;{color}\\  {color:#333333}scheme="https"{color}{color:#333333}&amp;nbsp;{color}\\  {color:#333333}secure="true"{color}{color:#333333}&amp;nbsp;{color}\\  {color:#333333}keystoreFile="/pathto/my.kdb"{color}{color:#333333}&amp;nbsp;{color}\\  {color:#333333}keystorePass="mypassword"{color}\\  {color:#333333}3. If you want Tomcat to use the default SSL port, change all instances of the port number 8443 to 443.{color}\\  {color:#333333}4. Add the keystoreFile and keystorePass directives to correspond with the keystore file and password that you are using.{color}\\  {color:#333333}5. Start or restart Tomcat using the appropriate startup script (startup.sh for unix/linux or startup.bat for windows){color} | |</property>
    

<property name="body">
h2. Check the location of all resources
{code}
sudo sudo crm_mon -1
{code}

h2. Migrate a resource to another node
{code}
sudo crm_resource -M -r api_ip -H halb2
{code}

h2. Move a resource back to its normal location
{code}
crm_resource -U -r api_ip
{code}</property>